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.
I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet.
The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet.
I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.
Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
How did you load the patch in your make file? I am adapting your patch to my device.
secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.
giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files
f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.
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
WARNING: This is ONLY for the Kindle Fire 1st Edition when setup as "OTTERX". Not to be used by ANY other Kindle Fire.
For more information on the OtterX project: go here
CyanogendMod 12.0 based on Android Lollipop 5.0
STATUS: ALPHA
REQUIREMENT: TWRP 2.7.1 or newer
BEFORE FLASHING ANDROID 5.0 the first time: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM (in TWRP).
STEP 1: Download SELF-COMPILED BUILD OF CM12.0 (some open review items are applied to this build):
https://goo.im/devs/Hashcode/otterx/cm12/
STEP 2: Download Android Lollipop-based GApps (by @dhacker29):
http://d-h.st/jzr
STEP 3: Reboot to recovery, wipe data and flash both .zip files (ROM first, then gapps).
STEP 4: Reboot again, and *WAIT FOR 8 - 10 MINUTES* while Android L is setup on your device.
CHANGES:
[11/30] Alpha build made public
CURRENT KNOWN ISSUES:
Initial setup can be *very* slow. *BE PATIENT.*
Google Play Movies needs DRM fixes, it won't work.
Current rotation settings starts the device in "Landscape", this may change
Some of the transparency settings are disabled due to low RAM. Needs work.
High battery drain while idle. 12%+ a day with wifi enabled.
WHAT *SHOULD* BE WORKING:
Audio
Wifi
Hardware accelerated graphics
Hardware accelerated codecs for audio/video
RESERVED FOR NOTES
XDA:DevDB Information
UNOFFICIAL CM12.0 for OtterX, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: OtterX Bootloader
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-11-30
Last Updated 2014-11-30
Screenshots
Screenshots
Reserved
Updated TWRP v2.8.2.0 for OtterX is now available here:
http://forum.xda-developers.com/showpost.php?p=50852364&postcount=3
This was built from Android 5.0 sources.
Downloading now
Welcome back Hash
Installed
1st boot took 7 or 8 minutes - like the man said BE PATIENT
Great work as usual.
Excellent! Kindle is as smooth as ever!
Sent from my Amazon OtterX using XDA Free mobile app
cheers mate, awesome as usual.
Sent from my Nexus 5 using Tapatalk
I notice many other devs are building odex type ROMs which save quite a few minutes on the initial boot.
My natural reaction is that the initial wait is worth not having odex type files which hamper user customization.
Just thinking outloud.
Also:
Right now some transparency settings are turned off due to low ram. Going to look into re-enabling.
Battery drain is high atm. 12%+ a day sitting idle.
I installed this rom and my otterx is running better than ever. It took 8:25 minutes to boot and a few more to set up. Thanks Hashcode!
Me thinks the gapps link is dead
Sent from my Amazon OtterX using Tapatalk
Hashcode said:
Also:
Right now some transparency settings are turned off due to low ram. Going to look into re-enabling.
Battery drain is high atm. 12%+ a day sitting idle.
Click to expand...
Click to collapse
If you can't stand to not have transparency and are willing to suffer some performance, you can turn the low_ram setting in the build.prop to false. (Until the performance setting is back that forces transparency)
Sent from my SCH-I545 using Tapatalk
Neoistheone2000 said:
Me thinks the gapps link is dead
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Links is working for me.
Welcome back Hashcode.
Its great to see You again in KF comunity !
Thanks for Your work, and help with lovejoy777's Slim.
Awesome! Any chance of you porting this to the 2nd gen?
Thank you very much! Work well!
Is there any way to bring back rotation settings? I need only 3 directions.
Any way to bring back to quick panel volume and sound options? Is not possible to turn off sound
Don't forget this is an alpha. All the extras will come with time☺
Sent from my Amazon OtterX using Tapatalk
Santehnik said:
Thank you very much! Work well!
Is there any way to bring back rotation settings? I need only 3 directions.
Any way to bring back to quick panel volume and sound options? Is not possible to turn off sound
Click to expand...
Click to collapse
For now I'm pushing the last 2 review items that we need to get OtterX back on CM nightlies for CM12. Then we can all sit back and watch the magic as CM does their thing re-adding all their UI changes.
Hashcode said:
For now I'm pushing the last 2 review items that we need to get OtterX back on CM nightlies for CM12. Then we can all sit back and watch the magic as CM does their thing re-adding all their UI changes.
Click to expand...
Click to collapse
The frameworks/native and hardware/ti/wlan ones?
Sent from my SCH-I545 using Tapatalk
Hashcode said:
For now I'm pushing the last 2 review items that we need to get OtterX back on CM nightlies for CM12. Then we can all sit back and watch the magic as CM does their thing re-adding all their UI changes.
Click to expand...
Click to collapse
Great job! Any chances of porting this to the Kindle Fire 2nd gen?
Thanks
I have 2 kindle fires. This question is for both, but since I am in the Kindle Fire area I it refers to the 1st generation fire I have.
I have a 1st generation fire. Currently it has the stock Amazon firmware on it. It started randomly rebooting. I want to remove the stock firmware and install a full version of Android that does not link this fire to Amazon. What guide should I follow?
you already have twrp and fff bootloader?
no. I have done nothing to to this.
system version 6.3.4?
Yes. 6.3.4
there are a few options
there are 2 different rom types Otter/Blaze and OtterX
OtterX is a more complex setup, but most of the newest roms are OtterX
I would select a rom from Random Builds and Development
or pick another one from the index [INDEX] Kindle Fire Development
post the rom you would like with full filename or link to thread
and I will post links to instructions
how about Otter -X with CyanogenMod
you understand that cyanogenmod is type of rom, with several versions, cm7, cm9, cm10...
pick one from the index
perhaps I did not provide enough information. CyanogendMod 12.0
http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155
That CM12 has been abandoned, and server that files were on has been shut down
You could try CM12 posted here http://forum.xda-developers.com/kindle-fire/development/random-builds-development-t3228941
You will need a PC to convert to OtterX
Download
zip-otterx-twrp-2.7.1.0-recovery.zip
otterx-u-boot_v2.05.zip
CM12 rom Zip (cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip)
Lollipop Gapps like http://opengapps.org/ ARM | 5.0 | Pico
See see [How To] convert to OtterX ROM/TWRP/Bootloader
Edit: Do not extract/unzip any of those zips