Related
i found the android vncserver project on google code and thought it would be a fun thing to have. so i taught myself how to cross-compile the android kernel. it is actually not that difficult. then i cried for help because the kernel patch was only available for an older kernel. after that i noticed it was actually a piece of cake to manually patch the kernel sources, as the patch was rather small.
so the result of all-night kernel compiling is the kkernel-1.0! mainly teknologists kernel and config, so still the props goes to him (and the others that worked on the kernel), my part was only patching the kbde keyboard emulator sources into the kernel and putting an update.zip together. this is compatible with mcr2.9, i didn't test it with other roms. should work with every rom that accepts the teknologist kernel.
the update.zip also places the fbvncserver binary (precompiled from the project page) in /system/bin. start with "adb shell fbvncserver", connect to heros ip port 5901.
now we just need to figure out how to send mouse events to the server and we're good to go!
as always no responsibility for your phone going berzerk (or your girlfriend )
somehow i am having difficulties uploading the file, please refer to modaco, i will try again later.
thread @modaco
It works great. Will be better when input is supported! Thanks
Hi all,
I have Fat Free Froyo installed with the latest 14th Jan 2011 kernel voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh edited to froyo & panel type 2 from t029000.massey.ac.nz but Google Goggles needs ipv6 support.
Is this a kernel problem or a problem with the build itself? I am experienced in linux, so can modprobe or insmod the ipv6.ko but I don't know where to get it from
Any help would be appreciated!
(message for kernel's developers) take this man! he can dev ipv6!
Jumping the gun there a bit
I triage bugs and work on stuff for Ubuntu. Have also ported a few linux bits to ppc64 (PlayStation 3).
I'm pinching the ipv6.ko from slayhers latest kernel build, hopefully that will work insmod-ding or modprobing it into the kernel thru the terminal on the Kaiser itself.
So, fingers crossed, this may be solved in 5 minutes!!
Didn't work, it must be compiled for a different platform...
Anyone have or know where to get a kernel for the Kaiser with ipv6 support, or failing that the correctly built ipv6.ko for the Kaiser so that it can be insmodded?
Getting it compiled in the kernel is the easy bit, although it does use up a lot of space which is limited in the kaiser's kernel so a little tweaking is needed. Getting it to work with the Kaiser's modem and the builds we currently use is a different matter unfortunately. It will take a bit of modding for it to work but it's more then achievable with a bit of free time. Wish i could buy that stuff!!If i get a chance i will get you the ipv6 module for the kaiser's kernel or a kernel with support for it so you can have a play.
I definitely look forward to it! If I knew how and what to modify I'd do it myself, but I thought arch-specific kernels had to be compiled on the arch itself? If that's the case, I can see how free time would be needed, it'd take hours or days to compile the linux kernel at 400MHz
I have compiled kernels before so if/when I learn how to do it myself, I could start to use my own git repo for more recent daily builds or something.
I'm also thinking about starting working on some *buntu stuff (I know Ubuntu is there for the Kaiser, but soem tweaks would help if I get a chance.)
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
xteejx said:
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
Click to expand...
Click to collapse
Yes, that is th correct make file to use. I have built the kernel with IPV6 support, haven't tested it but have attached the module to the post for you to try
Brilliant! I'll try it sometime within the next couple of days, although I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build, but I haven't economised too much.
I can see the the options for ipv6 in the ncurses menuconfig, so I guess it's just a case of enabling it and building the zImage right?
I seem to be having the old problem with the wifi though, and I know it's kernel related, but there are only patches for it, i.e. the wlan.ko, but can't see how to implement it myself so it's an all-in-one solution
When I get the hang of the Kaiser hardware properly, I might just push through a newer kernel from the armlinux site so watch this space
xteejx said:
I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build
Click to expand...
Click to collapse
How have you managed that??? What have you done?
I have no idea how it happened, perhaps the other devs add a load of useless options, but all I did was follow the instructions at that link above and compiled a zImage from the 2.6.32 arm branch, using the 2010 arm tools. Used NBHeditor to edit it for Kaiser, panel 2, froyo, flashed it and bang (not literally thank god).
I can't answer any better than that. I used the default options (for now at least) that the vogue build script uses for the kernel, but bluetooth, camera and gps work. No internet connection as yet either through the network or wifi, dumno what I've missed there, and no ipv6 (but can add that easily enough). Wifi doesn't work either, but I'm working on it, although that MAY be the reason why it's so fast...maybe it's missing a few options...still unsure at this point.
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
xteejx said:
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
Click to expand...
Click to collapse
That isn't true, all tested changes are pushed to git, you can see what has been changed and how from here: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
*facepalm!*
Didn't see that, will bookmark it and keep an eye on it, perhaps work with it. Thanks for the link
the androidhtc.com site is not related directly to the develop project because no developer is connected to it. Also the git repository it not hosted in linux to go but on sourceforge (so download the correct git). That site is very outdated.
wifi works if you use the correct branch (on sourceforge) and modules.
Am I right in thinking that http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD is the prebuilt kernels and nbhs from the source at http://androidhtc.git.sourceforge.n...og;h=62f075ddd13f378fd252be94c77e4f93d12584fb ??
I think I'm looking at the right tree now.
Flashing the latest NBH: VOGUIMG-320-FROYO-01-16-11.NBH still gives me the wifi error. Do I need to manually add the wlan.ko to it or ??
I could've sworn that an NBH I flashed before had all that in the NBH and it worked fine.
Ok, got it back to how I had it:
Flashed latest.NBH from http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD and dropped androidupdate.tgz to the /andboot folder of the SD card, installed update thru the boot menu and done.
So in reality there's nothing stopping me grabbing the same kernel source, building it and adding ipv6 support in the ncurses kernel config menu and making an NBH from it and flashing that over, and then doing the androidupdate.tgz, although I think with HTCFlasherGUI you can flash a zImage directly right??
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
xteejx said:
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
Click to expand...
Click to collapse
No, nothing wrong with it. Just do:
git clone git://androidhtc.git.sourceforge.net/androidhtc/kernel.git
You then need to set it to the correct branch using 'git checkout -b <branch you want> '
It's the 2.6.32 branch you are interested in, you can find out exactly what it's called using 'git branch -a' which will list the available branches.
Cool. Knew something went wrong somewhere, had to be me lol!
I added that ipv6.ko to the NAND via a androidupdate.tgz (only way I could do it), and it didn't work, something about incorrect module format (or something like that).
Are there any prebuilt kernels or NBHs for the Kaiser that include ipv6? Either as a module that I can insmod it in the terminal or built-in?
I hate being upstaged by people that can use Goggles without any problems.
I know slayher's kernels have ipv6, but I flashed the new stock one from http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/ and it didn't work. I mean the kernel did, but Goggles didn't - couldn't insmod it either - same invalid module format as the ipv6.ko scooter did for me
Also the git clone didn't work:
Initialized empty Git repository in /home/name/android-git/kernel/.git/
fatal: The remote end hung up unexpectedly
Links and rom updated:
ICS Sources build Image (Not SDK anymore, version 4.0.1_r1)
BIG, HUGE, MASSIVE, THANKS TO PAWITP FROM CM TEAM!!! (specially camera.aries.so, great job!)
FUGU kernel, linux 3.0, integrated voodoo sound and color (big thanks to renaudallard)
Here is the most recent image BETA 2:
Changelog on the second post.
We moved to google code:
http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
(ATENTION: image comes with a kernel for i9000b, if you have a i9000 international or vibrant, download the correct kernel)
Thanks to ytt3r for the vibrant kernel
Agreat tutorial made by ybinnenweg for installation and common issues (Thanks!):
http://forum.xda-developers.com/showthread.php?p=19563068#post19563068
How to root the rom:
http://forum.xda-developers.com/showpost.php?p=19175375&postcount=628
Github's:
http://github.com/onecosmic
http://github.com/syndtr
http://github.com/koaaN
http://github.com/pawitp
http://github.com/teamhacksung
http://github.com/cyanogenmod
IRC channel:
http://webchat.freenode.net/
##icssgs <- yes, double ## (we switched channel)
What works:
Both cellphones:
Hardware Acceleration
Audio
calls, sms, 3g - no more script needed.
Touch
Wifi
SDCards (internal and external)
Market
Contacts sync
Calendar sync
camera
panorama mode
face unlock
Gps
data usage
Partition schemma is now including datadata back to avoid issues with slow movinand devices
usb support
bluetooth
What does not work:
Camera (video recording)
Phone encryption
I'll be posting updates as soon as i have them.
CREDITS:
Pawitp: ril fixes, hw acc , camera lib hack(big android guy ).
teamhacksung
Cyanogenmod team
Syntr: kernel patches
Galnet : First Release
kooaN: i9000 kernel update
Thearc77 : google apps
WarDrake: mirroring
ytt3r: kernel patching, vibrant and captivate kernels
SGS CM team: ICS patches
Motafoca 3g switch apk
And all the other people that is helping to make this a reality
Cheers
Changelog:
Beta 2:
Adb now works at boot (previously it only worked after the phone full boot was complete)
PIN lock fixed (it should work, i cannot test it since i dont have pinlocked sim)
adb reboot recovery now reboot the phone to the recovery instead of performing a normal reboot
Recovery now allows you to make nandroid backups
Fixed Market download problem
Minor fixes (code cleanup)
Thank you Onecosmic
Enviado desde mi GT-I9000B usando Tapatalk
Subscribed! Thank you for your efforts and for everyone involved.
Sent via my GT-I9000 running CM7 (GB 2.3.7) using XDA premium
super cool onecosmic
*subscribed*
so that I'm not left in the dark about the latest changes via email
great work onecosmic !
keep it up
thanks !
subscribed, thank you for your efforts onecosmic! Wish you all the best
Subscribed. Gr8 work onecosmic.
mix tweaks-http://forum.xda-developers.com/showthread.php?t=1334818
+1, subscribed;
any chance of updating first post with link to github sources?
thanks
Really nice job, thanks a lot for this
Awesome job! No chance of doing a captivate version is there?
support you onecosmic
dunno a lot about kernel works but I can help about the system part.
anyway thank you
Is bluetooth working?
Is it safe to install this image. I just want to see how ICS is.. I may even report any bugs if I find, if that helps. Or should I wait for a stable release. I can't wait to see ICS, that's why
Please be gentle, thank you..
Sent from my GT-I9000 using XDA App
Guys, a couple of clarifications for those who ask by private and here:
This is an ALPHA release, means testing, developers, unstable. Not recommended for people whitout a minimum modding/development/rom playing experience.
I cannot work on other phones for a simple reason, i dont have one to test and the trial and error method is not an option (too many things can went wrong..)
All working features will be added to the first post (if is not there, is not working)
donate link is in the left side below my name (usual location on XDA)
Hope this covers all the questions.
Cheers
The colors problem is fixed? Or still we have the orange pattern?
Looking forward to re-igniting my (now)dormant passion for the good old SGS!
All the best!
I just had a little fun experimenting.
1) can you check the version of the kernel for I9000. Neither touchscreen ril worked when I installed. Swiping didn't work and my sim was never accessed.
2) I would not just try this as it might not work for everyone. I was able to install the system as an update to my cm7 installation. It has a nice update system where it converts contacts and calendar events to the ics standard. After it finished my phone froze and needed a restart. However after booting again, all my apps were still installed and angry birds worked. Looked a bit weird in those colours and swiping wasn't working at that point.
Oh and the colour issue seems to be like an overlay more than anything else. Menus that flicker show correct colours behind them. (If you bring up the power menu, the desktop behind it as it flickers is in the correct colouring). Or maybe the colouring and flickering are linked and it only appears like an overlay. (Fyi, hw acceleration may not help this. I used non hw accelerated roms in the past and there was no flickering on them like there is in this port).
Anyway its pretty exciting to be playing around with ics.
Edit: anyone wanting to test this should do a nandroid backup. I restored mine after testing and its as thought I never had ics installed (aka completely successful). Backup the nandroid on your pc tho. I am sure there will be work done on the sdcard which in theory could get wiped. (And many backups are a great idea)
Sent via my GT-I9000 running CM7 (GB 2.3.7) using XDA premium
Is safe, only do a nandroid of your actual rom/mod.
You must have your actual stock rom (odin one) with your pit, for unistall this rom.
Ps: really sorry for my basic english
richiebm said:
Is it safe to install this image. I just want to see how ICS is.. I may even report any bugs if I find, if that helps. Or should I wait for a stable release. I can't wait to see ICS, that's why
Please be gentle, thank you..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
drakenabarion said:
I just had a little fun experimenting.
1) can you check the version of the kernel for I9000. Neither touchscreen ril worked when I installed. Swiping didn't work and my sim was never accessed.
2) I would not just try this as it might not work for everyone. I was able to install the system as an update to my cm7 installation. It has a nice update system where it converts contacts and calendar events to the ics standard. After it finished my phone froze and needed a restart. However after booting again, all my apps were still installed and angry birds worked. Looked a bit weird in those colours and swiping wasn't working at that point.
Oh and the colour issue seems to be like an overlay more than anything else. Menus that flicker show correct colours behind them. (If you bring up the power menu, the desktop behind it as it flickers is in the correct colouring). Or maybe the colouring and flickering are linked and it only appears like an overlay. (Fyi, hw acceleration may not help this. I used non hw accelerated roms in the past and there was no flickering on them like there is in this port).
Anyway its pretty exciting to be playing around with ics.
Sent via my GT-I9000 running CM7 (GB 2.3.7) using XDA premium
Click to expand...
Click to collapse
Kernel for i9000 does not have the ril inside, ril is on the last image i've uploaded, you need to download and install the lastest image (first post) and then the i9000 kernel.
Its true that the negative color its a androidGLES problem, but the only working (so far) software GLES is the one that cames with the emulator, so enabling the hardware video chip will fix the color (since it is going to be rendered on real hardware and not in the softGLES)
Cheers
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.
Hi,
I am starting this thread because i have build CM10.2 from the CM10.2 repository and got it working.
I will post the progress here until XplodWild has started with the official development of CM10.2 and when he is releasing official or nightly builds.
This thread is just for those people who would like to have a preview of CM10.2.
All the things i did to make the build work came from the TF700 repository. So all the credits go to them. Offcourse all the changes i have made have been submitted to Gerrit.
@XpLoDWilD : If you do not agree with this thread, please feel free to remove this thread.
**********************************
Since the nightly builds have started I will not post any regular builds in this thread.
However since this is an experimental thread, I will post some builds now and then with some changes that I think would be nice to test
***********************************
What is working:
- Almost everything. Thanks to all the work of the TF300T CM team
- camera (flaky because focal force closes)
- dock is working
GApps: http://goo.im/gapps/gapps-jb-20130813-signed.zip
[20131012]
https://mega.co.nz/#!fQgCRYIQ!KaUk1zwbMxcScKdESXHelQsNy2gKmVn8A63Jpj_9hs0
[20131011]
https://mega.co.nz/#!bRx0na4I!UCi-MHhHm1ujmwl5gbH9NhE5kC11Ld5qukgiLb4OplA
[20131009]
https://mega.co.nz/#!HQYARRqR!YXMaYjFYv1EH464ZOaZZO3YVQ8I2tQ8CY-vLcVetjTs
[20130823]
https://mega.co.nz/#!KQxWjRzT!vehX_aGdh6EsGx08SmKMddp2Ac8x_Qvn5zeCv6ovLj8
[20130818]
https://mega.co.nz/#!7MYGjQoZ!ITRZkTlmZc98QKwczikXiyZTiVoxPIkLC6FOostpdXg
[20130809]
https://mega.co.nz/#!bVASBKSC!c1-GaVl0nOayqwMZBR4KXDjzKm1qxEfIu1TujWT0ZlM
[20130806]
https://mega.co.nz/#!GQRlXTwJ!WO_i8nHSp_GK0Ak_KIJodHabsbwPHTKX3E_nHWmnZug
[20130804]
https://mega.co.nz/#!qNpXlDBa!Pi6U1DlqrzX9cCEotD_XUReFH0QtTt887g3AQbvkdzk
[20130802]
https://mega.co.nz/#!mFRkzYAK!Q9Mf6S8c-ZBeFfQ3UhW9hgkaf6UovjVnIA8AAWtKJ2k
IMPORTANT:
This ROM needs the 4.2 bootloader. So make sure that you are on the 4.2 bootloader and that you have the correct TWRP version to flash CM10.2
ALSO... Do not forget that this is EXPERIMENTAL and you install this at your *OWN* risk.
[Changes]
[2013012]
- Wake on dock keypress
[20131011]
- Missed a commit for the LTO download
-
[20131009]
- added LTO download from tf700t
[20130823]
- Synced with cm
- Added CmAccount to the build
[20130818]
- off course all the changes from the cm repository
- new kernel updated by crmhoffman
[20130809]
- All the CM changes that are new
- multiuser now working
[20130806]
- All the CM changes that are new
[20130802]
- Kernel SELinux enabled in config.
- Focal seems to be working
- Youtube HD video playback seems to be working
Sweet, thanks.....first!
Sent from my Inspire 4G using xda app-developers app
4.3 google apps http://forum.xda-developers.com/showthread.php?t=2387878
---------- Post added at 08:20 PM ---------- Previous post was at 07:21 PM ----------
Just installed and synced after performing system wipe. One word: SNAPPY
Thanks for your work @scanno
TRIM support is a god send for this damn tablet. Thanks for all the work OP, sub'd.
great work man, it's running very smooth no lag whatsoever everything seems to work except the bugs you posted of course
EDIT: BUGS: NO root, ADB lists device as OFFLINE
noahvt said:
great work man, it's running very smooth no lag whatsoever everything seems to work except the bugs you posted of course
EDIT: BUGS: NO root, ADB lists device as OFFLINE
Click to expand...
Click to collapse
I have no problems with this. I have root and adb. If i do a adb shell i get a normal prompt, but i can su to root.
Did you enable root in the developer settings? Also i so get the offline statement, but that is when my laptop is not yet accepted on the tablet to be able to connect.
Hi
Bugs:
Focal keeps crashing when you record video and try to make picture, or try to make a picture with front cam
SU is installed without SU binary, binary cannot be updated, so no SU
If there is more than one screen of apps in drawer, when next app is installed trebuchet will crash if drawer is opened.
Overall, excellent work! Keep up.
What about dock in this rom?
I know its experimental but...
ch3mn3y said:
What about dock in this rom?
I know its experimental but...
Click to expand...
Click to collapse
Dock is working.
Sent from my Xperia T using Tapatalk 4 Beta
Was about to flash this. I will lose root if I flash this?
No. Its autorooted
Sent using tf300t - CROMI-X/Hundsbuah
The only bug now is video playback? and it doesn't even work on youtube?
soudy1994 said:
The only bug now is video playback? and it doesn't even work on youtube?
Click to expand...
Click to collapse
YouTube is working ok. I can play HD YouTube video
Sent from my TF300T using Tapatalk 4
Rom works great. The only issue I've had is spotty Wifi connection. I'm sitting 6 feet away from router and I only get 3 bars of wifi reception. It also disconnects often. I'm hoping it will stabilize.
Same here. Not that it is THAT bad, but wifi "quality" has worsen here
Sent from my TF300T using xda app-developers app
I got reboot after docking? Only me or rom bug?
And I always read that on cm, pa, aokp, pac man some keys on dock are not working but here every button works, awesome
EDIT: I dot have su ights? Any app wont take or give them...
If I understand correctly, su is handled differently with 4.3. I think I saw that chainfire or maybe it was koush got an app to get su like last week. This probably means that apps need to rewrite how they run su. Or something. I know that cyanogen(Steve kondik) was suggesting that instead of doing the su method, developers could rewrite their apps to extend the framework to make more powerful apps that don't need root. Sounded very interesting.
Check this out: https://plus.google.com/100275307499530023476/posts/SHyNpFuyo1E
please correct me of I'm wrong.
Sent from my Inspire 4G using xda app-developers app
I found chainfire thread and flashed supersu 1.51 (im sure 1.5, im nor sure with this .1) and i have root.
Just forgrt to edit post. Everything is fine. I was suprised that cm has no root
Sent using SO-01D - AuroraPlay/LuPuS_GB
andrewnelson23 said:
If I understand correctly, su is handled differently with 4.3. I think I saw that chainfire or maybe it was koush got an app to get su like last week. This probably means that apps need to rewrite how they run su. Or something. I know that cyanogen(Steve kondik) was suggesting that instead of doing the su method, developers could rewrite their apps to extend the framework to make more powerful apps that don't need root. Sounded very interesting.
Check this out: https://plus.google.com/100275307499530023476/posts/SHyNpFuyo1E
please correct me of I'm wrong.
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
You are right
In Android 4.3 SELinux is default (Security Enhanced Linux). At the moment su does not work the way it was. It has problems. CM10.2 is still in pre-nightly stage so problems like this can occur.