NFC with screen off-any good outcomes? - Samsung Galaxy Nexus

http://forum.xda-developers.com/showthread.php?t=1709586
Anyone tried this on our version of the galaxy nexus. I just got involved with nfc tinkering and to be able to scan while screen off would be great-though it sounds buggy currently.

I am using the other flavour (scan with lock-screen on instead of unlocking) from the developer and it is working great, no bugs or issues.

Can I ask what Rom you're running?

AOKP build 38

Related

[Q] AOKP JB Build Problem with 240 DPI

Hey guys, I have been an AOKP user since long. Have been using their Milestone6 until they released Jellybean builds.
Must say I am purely satisfied with these builds but have a small problem with this...Right now I am on JB Build 4.
I am getting tabs in two rows if I change the dpi of my phone to 240 or lower than that. 260 works fine though.
This never used to happen in Milestone 6. I am a 240dpi user and loves to see everything in one screen, but these two row splitting is annoying.
It happens in all the apps based on HOLO UI like Phone, People, Boid(3rd Party), etc.
Attached are the screenshots to explain my problem.
I tried looking into build.prop as well, but didn't find out what's the problem. Before reporting to AOKP guys, I want to ensure if this can be solved and this is seriously a bug or not!
Please help.
P.S: Landscape view doesn't have any problem. The problem persist only in portrait mode. However, Milestone 6 based on ICS never had any of such problems. Also, I know AOKP JB builds are still in their preliminary stage but this problem is a small things which I think need to be reported!
Use 241.
No visible change in applications other than fixes.
Thanks alot
Sent from my Galaxy Nexus using xda app-developers app

[Q] preliminaries prior flashing an A101

Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
VolkerPfosten said:
Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
Click to expand...
Click to collapse
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
pio_masaki said:
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
Click to expand...
Click to collapse
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
VolkerPfosten said:
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
Click to expand...
Click to collapse
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse
thats of cause comprehensible, since these iconias are quite old, right. And if i didnt needed the (3g)/hdmi (looking forward for ubuntu for android) i guess i would have baught an Nexus 7 aswell. However, in two weeks i got an exam and i'm investing way too much time right now in reading about all that stuff here so if you could direct me were to read about this 3g ril files or tell me how i can find them on the mashine i'll send it to you. I've read something about the build.prob but no mentions about 3g, cellular or ril or whatsoever in it. Also a "find" gave me nothing.
Unfortunately i have to read some annoying §&"/%§ now but i've set up the email notification now.
greetings

[Q] Recommended CM nightly?

Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Sgt7 rom works great
--
Sent from my mind to your screen.
Thanks!
elitelemming said:
Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Click to expand...
Click to collapse
I haven't noticed anything not working, and I've been on the nightlies since they started.
What things ate not working for you?
Sent from my MB860 using Tapatalk 2
chronicfathead said:
What things ate not working for you?
Click to expand...
Click to collapse
I may have spoken too soon, a few issues were just me not being familiar with JB 4.2 and how to set it up, couple of issues I've been having is that formerly full screen games and other apps are no longer hiding the on screen buttons (with the Amazon firmware there was a small pull-out tab to get them), though perhaps there is a configuration switch I am missing for this? Also some video appears to be tearing, though to be fair this might just be the video app... Also CM seems to be ignoring whatever I set the homescreen grid to be.

[ROM][4.2.2][CyanogenMod 10.1 Unofficial][TF300T(G) with BL 4.2][2013-05-09]

This is an experimental build of CyanogenMod 10.1 for Asus TF300T and TF300TG with the new bootloader 4.2.
If you are an experienced CyanogenMod user, please give it a try and let me know anything I broke.
But please see "Known Issues" below.
Would also be interesting to hear about results on different boot loaders.
Note that this is an unofficial build.
I will provide updates, as things are being fixed, but I don't plan to provide regular nightlies.
Instead I hope that my changes will be merged by CM, once all is working as expected.
Supported Bootloaders
Installed by Asus ROM v10.6.1.15.3 (aka bootloader 4.2).
Should also work with v10.6.1.8 (aka bootloader 4.2).
The current download does not work on the old JB 4.1 bootloader installed with Asus ROM v10.4.2.20.
Testing or fixing this is currently not a priority; even might not work at all.
Extras
Some extras I included that are not part of the official CM distribution:
My kernel patch to make DriveDroid work. See the app thread for more details:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Known Issues
Camera is crashing since 20130430 version. Sorry!
Audio and YouTube videos play about 9% too fast. MX Player works fine.
[WHEN CAMERA WAS WORKING...] Setting camera to burst 20 pictures will stop after 8-14 on average.
No radio on TF300TG.
Downloads
Get the latest version:
cm-10.1-20130509-EXPERIMENTAL-tf300t.zip - 160.11 MB
Older downloads for comparison:
cm-10.1-20130506-EXPERIMENTAL-tf300t.zip - 160.21 MB
cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB
cm-10.1-20130428-EXPERIMENTAL-tf300t.zip - 163.58 MB
cm-10.1-20130427-EXPERIMENTAL-tf300t.zip - 163.58 MB
The latest source code is available from branch cm-10.1 in these two repositories:
https://github.com/f69m/android_device_asus_tf300t
https://github.com/f69m/android_kernel_asus_tf300t
For more details, please see "Building from Source" below.
Changes
Coming Soon:
Fix audio, when keyboard dock is connected; unfortunately this removes support for USB audio.
2013-05-09:
WLAN and audio working on TF300TG.
Small fix for camera, but not working yet.
Properly setting Bluetooth MAC address.
2013-05-06:
Bluetooth working fine for me.
WLAN should be stable for everyone now.
libsurfaceflinger is built from source again, the segfault is fixed.
The screen flickering is definitely gone; running really smooth now.
2013-04-30:
Updated all blobs and config files.
Included libsurfaceflinger from Asus to avoid segfault.
Include patch for DriveDroid.
2013-04-28:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
2013-04-27:
New kernel based on Asus v10.6.1.8.4.
Some blobs and configs updated.
These are only the changes made by myself and jsfrk specifically for this build.
The latest changes from CyanogenMod are also included, but not explicitly listed.
Instructions
This experimental ROM is targeted at experienced users that can help test and make it work.
If you are new to CyanogenMod and you need instructions on how to use the download, it is not for you yet. Sorry!
Building 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 cm-10.1-tf300t
You can also run this command in an existing repository.
Credits
The whole amazing CyanogenMod team.
jsfrk for testing and fixing issues on TF300TG.
Asus for breaking bootloader compatibility again.
First download is available!
Of course in my "final" build, I had borked WLAN.
So did a "more final" build, which is now available for download.
Just confirming, it does NOT work with the 4.1 bootloader. The boot animation freezes.
Just another reason for me to update my tablet this weekend. I'll be flashing this for real some time today. Thanks.
Update available:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
Really awesome rom! very quick and smooth. But the screen keeps flickering.
crazynitro said:
Really awesome rom! very quick and smooth. But the screen keeps flickering.
Click to expand...
Click to collapse
Yes, I noticed that too.
First step is to update the graphics drivers, I hope that will fix it.
Still getting a segfault with the new drivers though.
Thanks for your feedback!
Sent from my TF300T using Tapatalk HD
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Downtown taco said:
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
Click to expand...
Click to collapse
Hmm, not sure, what you mean with "internal tester"? But I am sure happy about everyone giving feedback, thanks!
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Click to expand...
Click to collapse
Have not seen any WLAN disconnects yet, but indeed, the whole WLAN and Bluetooth code needs redoing (same chip, same driver).
When trying to fix Bluetooth, I usually break WLAN completly, without making Bluetooth work properly.
Next update will be mostly blobs and config files. Doing that slowly to figure out, where that segfault is coming from.
After that will restart the WLAN/Bluetooth code from scratch. Well, from the Asus code that is.
Currently using the code from official CM BL4.1 kernel.
New download that has now all blobs and config files updated!
Seems the random screen flickering is gone, please let me know, if you still see it.
Well, being a bad boy, I included libsurfaceflinger from Asus, though this should really be the one compiled from the CM sources.
But for now it avoids a segfault and it seems OK, while we have worse issues with WLAN and Bluetooth.
Also included a little extra patch that has not been merged into the official CM kernel.
It makes DriveDroid work on our beloved TF300T. For more details see the app thread:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Sorry, I don't have access to a TF300TG, so can't test it.
Of course I am happy to clean up and push out my current sources, if there is a developer who wants to port it to the TG.
Otherwise I'd save the time for cleaning up now and push it out, once I am happy.
Sent from my TF300T using Tapatalk HD
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
f69m said:
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
Click to expand...
Click to collapse
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Sent from my Galaxy Nexus using Tapatalk 2
Downtown taco said:
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Click to expand...
Click to collapse
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
f69m said:
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
Click to expand...
Click to collapse
It's always the camera...
Sent from my Galaxy Nexus using Tapatalk 2
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Sent from my ASUS Transformer Pad TF300T
pcoussa said:
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Click to expand...
Click to collapse
Thanks!
Yeah, luckily I have a very strong head, so eventually the camera will have to yield.
Temporarily the camera has won though; I put it aside and first looked into WLAN and Bluetooth.
Good news is, here I am hearing music via Bluetooth from my Laptop speakers!
And even after switching off and on.
So I guess there will be an update later today with WLAN more stable and Bluetooth working.
We are also working on WLAN on the TF300TG and have that somewhat working, too!
Though might not be in today's release yet.
Sent from my TF300T using Tapatalk HD
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
f69m said:
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
Click to expand...
Click to collapse
I'll give it a run later tonight
Sent from my Galaxy Nexus using Tapatalk 2
Hmm, 10 downloads and no one speaking up so far...
I take that as a good sign!
More good news: we got WLAN working on TF300TG too.
There are still issues with sound though.
Is there any developer with a TF300TL around? Would be great to cover the lot!
Currently updating my Ubuntu Touch port to the new code for BL 4.2.
Apart from getting some work done on UT, I hope that using Ubuntu, I might gain another view on the camera issue.
It's so frustrating: everything between the Android camera HAL and the kernel is a black box. No documentation and no source code.
Just some error messages in logcat and some in dmesg... but why?
Sent from my TF300T using Tapatalk HD

[Q] Recommendation for most stable custom ROM?

I've been a long-time flashaholic, but I've grown weary of all the FCing, wonky GPS, camera issues, bluetooth issues, etc. with many of the popular custom ROMs. I've gotten to the point where I do not need the latest and greatest ROM with all the fancy bells and whistyles and just want something that works well and is stable. I prefer AOSP-based (need tether to work), but do not need Kit Kat-based. So, recommendations?
CyanogenMod 10.2 + xposed framework
Sent from my SGH-T999 using Tapatalk
Yea, did this, but GPS is wonky (sometimes takes over 30 minutes to find me), bluetooth will not connect, and lots of random reboots/freezing. And, this is on the stable release!
Miracast screen mirroring is broken on CM 10.2. I get best results with AOKP 4.3. All KitKat ROMs have broken Miracast, BTW. If you need working MHL/HDMI out, you have to use a Touchwiz ROM, unfortunately.
cccheel said:
Yea, did this, but GPS is wonky (sometimes takes over 30 minutes to find me), bluetooth will not connect, and lots of random reboots/freezing. And, this is on the stable release!
Click to expand...
Click to collapse
Try the gps fix in the sticky roll up
Sent from my SGH-T999 using Tapatalk

Categories

Resources