Develop Bugs

Enabling NFC on CM10 for S3? Maybe I'm just blind?

So I searched for the answer, but everyone seems to say that GW is working on CM10...I did get it installed with the workaround, but what I'm finding is that in my Settings app in CM10, that there is no NFC option. Am I just blind and missing it in a different menu, or why does it not show up? I'm using the newest 7/29 stable build.

dubbactrumpetmsu said:
So I searched for the answer, but everyone seems to say that GW is working on CM10...I did get it installed with the workaround, but what I'm finding is that in my Settings app in CM10, that there is no NFC option. Am I just blind and missing it in a different menu, or why does it not show up? I'm using the newest 7/29 stable build.
Click to expand...
Click to collapse
Don't hold this answer against me, but I am pretty sure that the NFC drivers are absent, Since CM10 is still in preview phase.

codyrichards said:
Don't hold this answer against me, but I am pretty sure that the NFC drivers are absent, Since CM10 is still in preview phase.
Click to expand...
Click to collapse
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.

zmore said:
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.
Click to expand...
Click to collapse
So I'm curious...on CM10, where should the settings be? Am I missing something, or should I reflash? Also...my soft buttons are gone?! Just the lights...they still work...

WOW!
I thought I was loosing my mind. I'm glad I'm not the only one having this issue. I scoured these forums so much today my phone ran out of juice around noon. I wonder why some S3 747 users are having issues and others aren't. I have the AT&T variant and am using the 07/29 preview release just like the other posts. I have already done all the wallet fixes, but can't seem to find how to turn the nfc on either. Can you tell us the work around you used to get yours to work?

I'm having the same problem, NFC options do not appear in settings and Google Wallet states that NFC is disabled. This is on an ATT SIII, running CM10.

Exactly...no idea on my end. I'm also finding that Android File Transfer doesn't work, so I can't use my new SD card...I also cant back up, since my current one is full...feeling like Im stuck for now.

zmore said:
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.
Click to expand...
Click to collapse
You're running the preview build, right? Did you have to do anything to get NFC running or was it enabled by default?

So... By any chance, did you miss a step in the wallet workaround install? I had the exact same problem. Ended up having to wipe and reinstall my rom. Then follow the wallet workaround instructions exactly. Also, if you ever installed wallet from the market, go in and make sure auto update is unchecked. If you look at the original wallet thread in the development forum you'll see this happened to a couple of folks. Not sure of the cause, but I know that I had to reflash and also disable that auto update. I'd recommend a nandroid right after you reflash a clean rom and verify that nfc settings are there (under wireless - more).
HTH
Good luck!
Sent from my Galaxy Nexus using xda app-developers app

Settings------> more settings.
Sent from my rooted SGH-I747M

thecoach1999 said:
Settings------> more settings.
Sent from my rooted SGH-I747M
Click to expand...
Click to collapse
Thanks for that, but that was the first place I checked...since that's where it always is. The whole problem from the beginning was that it wasn't where it should be.
Anyway....
Good news. I found a workaround if it's missing. If you install CM9, make sure its there, then do a no-wipe install of CM10...there it is. Not sure why that works, or why it's missing in at least a few people's downloads of CM10, but that's my workaround. Going to try the newest version wallet workaround now and make sure it works.

I'm running into a really strange problem... while running a clean install of CM10, NFC is available in the menu. However, after installing Google Wallet via this method:
blog.tekkidd.com/2012/07/howto-install-google-wallet-on-att-samsung-galaxy-s3-sgh-i747
the settings option for NFC disappears.
I can run NFC by going through root access and installing nfc.apk from the app folder, however, this makes the phone EXTREMELY unstable, and it will begin to freeze up every few minutes. For the time being, it looks like the best option would be to wait for Wallet compatibility to be improved in the coming updates.

That is really weird. What I did was flash CM9, then CM10. (now I'm on paranoid android...but anyway). NFC was there, then I used the method listed in the Q&A section to load the newest version. Of course, when I went to McDonald's to use it...it failed...as it always has ( I had the Verizon Galaxy Nexus at one point). I've never seen NFC actually work for real. I don't know what it is, but maybe the people that run the businesses don't have it turned on correctly. I was really wanting to see it work too.

[Q] Using Tiny's CM10.1 rom and Netflix issues

Hi, rather new here so I can't post in the thread on the developers board. Thought I'd try here. I recently flashed Tiny's latest CM 10.1 nightly rom and I really like it so far. There are a couple of issues but after messing with it for a while, it's mostly smooth and works well. My biggest beef, aside from those couple issues is Netflix. The app loads and I can select a show, but when I try to load a video, I just get the red loading screen that goes on forever until I hit the back button. I tried an older apk, and it wouldn't load, period (1.5.2), which I guess is to be expected when running Android 4.2. I tried 2.1 and I got the same issue with the red loading screen. Tried loading it in the browser and I got the usual page that tells me I need a certain browser for it to work. The app worked just fine in the official CM 7.2. Is there an option in settings I'm missing or something or does it not work on this rom (which I don't see why it wouldn't)?
Other naggy issue is epsxe. It works alright but if I press a volume button, it either increases or decreases all the way and all buttons freeze. Nothing works. Home, menu, power button, touch, etc (yet the emu keeps going and the music keeps playing). Sometimes when I press an on-screen button to move, it's like the button gets stuck and the character keeps moving in that direction. I have to remove the battery to reboot. Did not have this issue in cm 7.2.
Other than that, awesome rom and thanks, Tiny, for working on it.
EDIT: Well, I just tried using epsxe again and it even worked when using the volume button. Not sure why it worked except that I let the game load for a bit before pressing anything. After that, it worked just fine. So, I guess it may be even an app issue on 4.2, rather than the rom. Hope Netflix is as easy to get working.

Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...

omniatic said:
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
Click to expand...
Click to collapse
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.

Kaepernick said:
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Click to expand...
Click to collapse
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.

Kaepernick said:
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Click to expand...
Click to collapse
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?

Kaepernick said:
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Click to expand...
Click to collapse
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.

tiny4579 said:
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
Click to expand...
Click to collapse
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?

Kaepernick said:
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Click to expand...
Click to collapse
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.

ealassi content
tiny4579 said:
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
Click to expand...
Click to collapse
Tried it. Not sure if I did it right. Most likely not. lol But in any case, it doesn't work. Getting a bit tired, so I may just relent. I'm sure many who are more experienced have tried already.

Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.

MysticCobra said:
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
Click to expand...
Click to collapse
I like Jelly Bean. I like how it looks and feels. It's a more mature Android. Plus, I like keeping up to date with software. It's kind of nice to have 4.2 running on the aging, yet good o'l Dinc, when some newer devices don't even have 4.1 yet officially.
Also, I got it working, by the way! Before, when I downloaded the newest one onto 10.1, it would just continuously load when picking a video and not work. After tinkering, I got it to play sound but no video. I could tell that the video player was different than the one I used on 7.2 (also, the newest app). I switched back to 7.2 for a bit and downloaded my apps. I backed everything up using Clockwork mod so I could go back to it whenever. Then I backed up all the Apps with Titanium Backup. I switched back to Tiny's 10.1 and restored the apps. I tried out Netflix and it worked. It was using the same player it used on 7.2. I don't know if it detects Jelly Bean when you download it from Google Play or if it does it when you sign in to your account. When I restored it, I was already signed in, so maybe that's it. At any rate, it works.

Well, I spoke too soon. It did work for the first few videos but then stopped. I tried uninstalling and reinstalling with the Titanium Backup, but when I try to choose a video, it says I've been signed out. I sign back in and I'm back to the forever loading red screen. So yeah, I think it detects which OS I'm on as I sign in. Just a guess though. Just shows that it has nothing to do with your ROM aside from their newest player not working properly on it. It can indeed be fixed via the software with some tinkering.

Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.

tiny4579 said:
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
Click to expand...
Click to collapse
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.

Kaepernick said:
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Click to expand...
Click to collapse
Hmm, if you edit that file back to 9 and open Netflix does it work?

tiny4579 said:
Hmm, if you edit that file back to 9 and open Netflix does it work?
Click to expand...
Click to collapse
Yes and it didn't work. Then I tried "6". Didn't load. I tried 9 again and for whatever reason, it loaded. It works just fine now, using the same player it did in 7.2. The kicker is that I check the XML file again and it changed somewhat. It now says "6" and it looks different. I believe the Player line used to be before the Logged in line. Now the logged in line is last. If there was some way to force it to use 6 every time, even when logging in, we'd have a working netflix app on your rom.
Maybe "old app version=17" is the key, I don't know.
EDIT: Exited the app. Still works. Rebooted the phone. Still works. There's no log out button, so I assume to log out, I need to clear data, which I assume would just put me back at square one. Seems to be working fine now, as long as I stay signed in. If I somehow have to sign in again, I'll check the xml file.
Attached the file. Just edited the user id part.

Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.

Watching this with interest, if you guys figure it out please post a guide and link to it because you're not alone. My Netflix stopped working when I upgraded to 10.1 as well (interestingly it worked fine on my ICS One-Click ODIN Rom that I got last June, not CM) and this was the first thread to pop on my google search as I've started looking for answers.
*UPDATE* Got mine working using the directions in this thread: http://forum.xda-developers.com/showthread.php?t=2101525
Hope this helps!
Kaepernick said:
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Click to expand...
Click to collapse

[Q] Parental Control

So I want to buy my 9 year old son a Nexus 7 after seeing how he uses my computer for his project research, school math challenges, etc. I also see the value of buying him appropriate books on Amazon as he has a requirement to read at least 20 minutes a day. Furthermore I also noticed how he takes our mobile devices, takes photos and experiments with various filters (to a point the mother uses one of his creation as her profile picture). That is the innocent and good side of things ....
I however cannot see any build in parental control functionality in Android that will assist me in keeping it as clean as possible in terms of content visibility on the Play Store, Internet browsing and managing time.
What are my options? I am willing to pay extra if needed if there is something a parent has used successfully.

I think you can create for him a limited profile, but being that I'm not sure, my youngest is 17
Sent from my HTC One using Tapatalk

z0phi3l said:
I think you can create for him a limited profile, but being that I'm not sure, my youngest is 17
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I cannot seem to find anything in that regard - this is very sad. I was hoping I can give him a Android based device but there seem to be no parental control function on Android (never mind anything build in). I keep on snooping around ...

One of the problems I also cannot seem to find anything is because I am using CM11 on my Samsung S3 which does not have the multi-user functionality (not to be confused with profiles).
http://asia.cnet.com/how-to-set-up-parental-controls-for-android-62222756.htm basically sums it up. So in other words I have to stay stock with 4.3 > otherwise I loose out.

There are Users or Profiles or something like that in Kit Kat. I don't have my tablet with me so I can't direct you how to do it. But yes you can make one for "Son's Name" and he can only access specific apps.

Cares said:
There are Users or Profiles or something like that in Kit Kat. I don't have my tablet with me so I can't direct you how to do it. But yes you can make one for "Son's Name" and he can only access specific apps.
Click to expand...
Click to collapse
If I buy the Nexus 7 will I be able to upgrade to a official build of 4.4 or do I have to grab a custom ROM?

1-0-1 said:
If I buy the Nexus 7 will I be able to upgrade to a official build of 4.4 or do I have to grab a custom ROM?
Click to expand...
Click to collapse
Should be no problem getting the OTA at this point.

[PORT][UNOFFICIAL] Cyanide-L for d2tmo (5.0.2 Lollipop)

All credit to this ROM goes to rogersb11. The only thing I did was change the install script so that it works on the d2tmo. With that said, this is an unofficial ROM and is not supported in any way by the original developer. That means don't go bugging rogersb11 with any questions about this. It is unsupported. It is only here so us d2tmo users can enjoy his kick ass ROM until and if there is an official port.
I will help in any way that I can, this is what I am using for my daily driver right now and I love it.
The camera does not work. I don't use my camera much, so I am fine with that for now. If you need a working camera, then this is not the ROM you want on your phone.
A few notes before install.
Thanks to rogersb11 for the Cyanide ROM, TheGeekyNimrod for the d2att port, without which I could not have done this, and leonid002, because without his assistance, I would not have even known how to do this to begin with.
First let's discuss the bugs:
The AOSP Keyboard will continuously crash on you from the first boot. Make sure you have a Google keyboard APK at the ready. This ROM comes with ES File Explorer, thanks to rogersb11, who put the ROM together in the first place, so you should have no problem installing any APKs you need to install, even before replacing the keyboard.
Install Google keyboard, then disable your AOSP keyboard. One this is done your keyboard will work just fine.
The phone will self report as the i747, that is where this ROM came from. As soon as I find what I need to change to fix that, I will update.
I believe the camera bug is still here, havent tested it yet, so just download Nexus camera from the Play store.
Other than that, works great so far.
Anyway, now it is time for the... Wait for it...
DISCLAIMER:
Despite the quality of this ROM, it is an ALPHA build.
Neither I, or any developer is responsible if you brick your device in any way, you're neighbor steals it, your nephew flushes it down the toilet, or you somehow travel back in time to an alternate 2012 where the world comes to an end in December, resulting in your phone being destroyed. Any damage to your device is YOUR RESPONSIBILITY.
You should be able to use any current Lollipop gapps with this ROM.
INSTRUCTIONS:
Download ROM below
Install a recovery if you don't have one (I use TWRP Multiboot, found in this same forum)
Factory reset (wipe Dalvik, cache, you know the drill)
Install the ROM (link below)
Install Gapps
Reboot into Cyanide
Install Google keyboard (or maybe your favorite alternative, SwiftKey works, not sure about anything else yet)
Disable AOSP Keyboard
Enjoy.
CYANIDE ROM DOWNLOAD:
1-02-2014 https://www.androidfilehost.com/?fid=95864024717074572
12-28-2014 https://www.androidfilehost.com/?fid=95864024717073794
XDA:DevDB Information
Cyanide-L Alpha d2tmo, ROM for the T-Mobile Samsung Galaxy S III
Contributors
reeferbob, leonid002, TheGeekyNimrod,
rogersb11,
Source Code: https://www.androidfilehost.com/?fid=95864024717073794
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-01-02
Last Updated 2015-01-02

One thing I like about this ROM over CM12 is that the option to adjust your DPI is baked right in. Another is the darker theme, and the fact that you can wake with the Home button once again.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app

Thanks OP
Downloading now
?

This thread is now opened and continue.
Edfunkycold
Have a great day!

Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

reeferbob said:
Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
another rom to play with thank man

In the future, I do plan to start officially building this for d2tmo. Just got a few things to get straightened out before I do. I have the device trees and everything, just gotta tie up some other ends before I dive into supporting two devices.
That said though, I will need testers as I don't own this particular device, and maybe someone to help d2tmo users trouble shoot problems that crop up specifically for their device.
Sent from my SAMSUNG-SGH-I747

Masterloki666 said:
Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
So I've been running this all day and coming from latest nightly build this isn't bad at all still has some work to be done but its loli-goodness on our ol s3 that being said I did have a few hangs when listening to Pandora when trying to turn on screen an switch songs was at work an unable to see what exactly happened anyone else ? BTW thanks again
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

The only things I've noticed so far are as follows:
Firefox makes Metro PCS think I'm tethering for some reason, except for, ironically, when I have request desktop site checked. Opera works great though. Not to mention, if you make sure to go into the settings and put Opera on Phone mode, the look and feel of it just kind of flows with Lollipop's multitasking cards, just horizontally scrolling and vertically closing.
I heavily dislike Chrome, so I don't use it, and couldn't tell you if it works or not, because I haven't installed it.
The stock browser kind of hung on me one time, but I haven't been able to make it happen again.
The phone shuts off without warning, it seems as soon as the battery goes down to 14%
As far as Pandora, I really haven't installed it, because I have Rhapsody. I may give it a shot and see what happens.
The Firefox issue probably has something to do with the lollipop user agent, as I know that this is how Metro blocks tethering. Still weird that it works fine with the other browsers though. Anyway, due to issues beyond my control, I probably won't be online for about two weeks after today, all my bills came up due at once so my phone bill will have to wait until next payday. The extra days off work the week of Christmas really put a strain on my finances. Sure I'll probably hit a hotspot from time to time, but my phone is my main internet connection at home. Hell, it's faster than cable internet or even any DSL connection I've ever had, so why spend the extra money? I'm really surprised how well MetroPCS works in Denver, even without an LTE phone. The HSPA+ is plenty fast. Before the T-Mobile deal, I had a Metro CDMA phone, in Texas, and it was atrocious.
But yeah, I have WiFi at work so I can keep checking in from time to time when I'm out on a smoke break, plus, I'm definitely keeping an eye out for new developments.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

I just got the new build installed, the dark color scheme is awesome. I just left in the check in the installer script for the d2att this time, and added one for d2tmo, maybe it will help anybody who may be testing across multiple devices.
In this one I've noticed the AOSP keyboard is working fine so far.
I will upload it as soon as I get the chance.
If you dirty flash over the previous build, make sure when you install the new build to reinstall the gapps. After its finished wipe the cache and dalvik, otherwise Google Play services will just keep crashing.
After reinstalling gapps, wiping the dalvik and cache, I got one Google play services error, but it hasn't seemed to affect anything.
Everything about this is the same as the build from rogersb11, I just edited the install script so that it installs on d2tmo as well. Just like the earlier build, it will be unsupported. There are bugs, and on an early build, that is to be expected. But so far, I've definitely seen an improvement.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Installed and running pretty smooth. The previous build would randomly advance my clock by 5 hours and would show all incoming calls as from "private". The new build however does none of those things.
So far on the new build, music has crashed once but relaunching it fixed that. I was not sure what nexus camera to get, not to mention their permissions were a bit crazy so I went with Open Camera and it works fine.
Thanks for taking the time to make and port this. The t999 is starting to fall to the way side and I cannot afford a new device so being able to run 5.0 is a blessing.

Working perfectly Thanks to all the devs over at d2att right How come no devs have d2tmo?? Smh.

No SIM
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???

Try installing the older build first, and then install gapps, let it run it's first boot, and let everything set up. Then reboot into recovery, and install the later build, reinstall gapps, and wipe cache and Dalvik. Then boot again as normal.
This has resolved a couple of issues for me, although I haven't gotten the insert SIM message with either of these builds. Can't thoroughly test anything until the end of next week though, my phone service is cut off until I can pay my bill on the 15th, and my WiFi reception where I'm at is spotty at best (on all my devices).
Also, I am on MetroPCS, not T-Mobile, I'm just using the T999 on their network.. Which I guess is also the T-Mobile network. Not sure if there are any major differences or not.
The only issue I've had was with su, and after installing SuperSU, a couple reboots, the last one was after changing my DPI to 240, I was able to gain root access.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
You may need to update your modem. I don't know about the T-Mobile modems and their availability, but for most using d2att in any LP rom, this has solved that issue.
Sent from my SAMSUNG-SGH-I747

I just installed it on my t999l. Will report back how it runs. Thanks for the ROM.

jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?

goldentequila said:
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?
Click to expand...
Click to collapse
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.

jonesin said:
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.
Click to expand...
Click to collapse
Thank you. I'll try that.
---------- Post added at 04:31 AM ---------- Previous post was at 04:29 AM ----------
goldentequila said:
Thank you. I'll try that.
Click to expand...
Click to collapse
OK. I encountered one major issue that was a bit scary. Everything was working fine at the first boot (except for the sim card). But, I turned off my phone. I then powered it back on, but it wouldn't boot into Android. It would just get stuck at the initial boot screen and go black. I was able to fix this by removing the battery and restarting it. If anyone experiences this issue, try that.
I tried turning off my phone to boot into recovery, and the same problem happened. I'm going to reinstall the ROM and see if the problem goes away.

General GrapheneOS is available for the Pixel6/6Pro

GrapheneOS​The private and secure mobile operating system with Android app compatibility. Developed as a non-profit open source project.
website : https://grapheneos.org/
WebUSB-based Installation : https://grapheneos.org/install/web
CMD Line Installation : https://grapheneos.org/install/cli
Releases : https://grapheneos.org/releases#raven-stable
This is listed as "Experimental"...

Not to sound like a broken record but with no play services do Google Photos and app updates work with that "sandboxed Play services compatibility layer" mentioned on they site?

Android-Desire said:
Not to sound like a broken record but with no play services do Google Photos and app updates work with that "sandboxed Play services compatibility layer" mentioned on they site?
Click to expand...
Click to collapse
yes. works very well (as long as you install all 3 parts of sandboxed play services). I would maybe wait a few days before installing it on the Pixel 6. but using A12 on my 3xl and everything works, photos, gboard, official gcam (all running with network access disabled).
Also, GrapheneOS for Pixel 6 still says Experimental on their download page (it might just need to be updated). But if you're okay with maybe experiencing some bugs, it should work fine (but as stated above, most should wait a few days, they're very good on updating - especially the first few weeks after release)

Good to hear about... will be watching! cheers

I basically bought my P6P for this, so I'm extremely happy development is moving forward! Really hoping that, when a stable version is out, it will be possible to use the phone "normally" with it. Keep it up, Graphene team!

I'm with @Alex-Absolute I purchased my P6 just for GrapheneOS support, coming from a string of OnePlus devices. Though I am going to wait until it's listed as stable to switch, I'm excited they have a working build going!

I've got the release page in Windows' Aignes Website-Watcher, set to look for changes after "Pixel 6 Pro" and before "Version", so I should know when it changes to Stable.

roirraW edor ehT said:
I've got the release page in Windows' Aignes Website-Watcher, set to look for changes after "Pixel 6 Pro" and before "Version", so I should know when it changes to Stable.
Click to expand...
Click to collapse
Amazing, thanks for the tip!

Alekos said:
yes. works very well (as long as you install all 3 parts of sandboxed play services). I would maybe wait a few days before installing it on the Pixel 6. but using A12 on my 3xl and everything works, photos, gboard, official gcam (all running with network access disabled).
Also, GrapheneOS for Pixel 6 still says Experimental on their download page (it might just need to be updated). But if you're okay with maybe experiencing some bugs, it should work fine (but as stated above, most should wait a few days, they're very good on updating - especially the first few weeks after release)
Click to expand...
Click to collapse
I used GrapheneOS on my 4a during most of the Experimental days, and i did not experience 1 hicup. I would compare their Experimental Builds to Android 12 Beta. So it's nothing to be afraid of. It's definitely ready for daily use in my own opinion....

Are there any screenshots of this OS? I always like trying new things but I'm thinking there isn't much to look at that would be different from a standard Android OS

Alex-Absolute said:
Amazing, thanks for the tip!
Click to expand...
Click to collapse
You're welcome, I'm using the free version - it's been around for a very long time on Windows, and I'm using the Android app which appears to more or less sync with the Windows version through Dropbox, if you have or create an account with Dropbox. It doesn't work perfectly for me, but I at least get notifications on my phone about the same changes in websites that the Windows program lets me know about - so I at least know that I should get on the computer and look to see what's new.
Sorry to anyone for the OT - I have lots of Android-related sites set to give me notifications of changes through this program.
The non-free version is a little pricey for my needs.

RetroTech07 said:
Are there any screenshots of this OS? I always like trying new things but I'm thinking there isn't much to look at that would be different from a standard Android OS
Click to expand...
Click to collapse
I will post some screens later this evening...

I've wanted to switch to this for a long time (It's actually a huge reason I switched back to the Pixel series) but I'm not sure if I can commit to losing Android Auto

AndroidAddict420 said:
I used GrapheneOS on my 4a during most of the Experimental days, and i did not experience 1 hicup. I would compare their Experimental Builds to Android 12 Beta. So it's nothing to be afraid of. It's definitely ready for daily use in my own opinion....
Click to expand...
Click to collapse
I agree. I've been using it off and on for 18 months on different pixels. but just good to be cautious, as always...
GrapheneOS just tweeted a few hours ago, the next release will be Stable for the 6 series (most likely this week)

Alekos said:
Also, GrapheneOS for Pixel 6 still says Experimental on their download page
Click to expand...
Click to collapse
What I read about that is that its not experimental in the "unstable" sense, its that they haven't fully implemented the security enhancements.

Flippy125 said:
I've wanted to switch to this for a long time (It's actually a huge reason I switched back to the Pixel series) but I'm not sure if I can commit to losing Android Auto
Click to expand...
Click to collapse
Given the sandboxed mode for play services, do you really have to lose auto?

The.Jericho.Initiative said:
Given the sandboxed mode for play services, do you really have to lose auto?
Click to expand...
Click to collapse
Good question. Last time I looked into it, AA was a no-go. Guess there's only one way to find out. I'll report back later if it works or not
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Other than that+call screeening, this build is solid for an "experimental" build (Tbh they could have put the stable flag on this, but I assume they are waiting for bug reports before doing so). If anyone is looking for a good de-Googling solution, this is it.

Flippy125 said:
Good question. Last time I looked into it, AA was a no-go. Guess there's only one way to find out. I'll report back later if it works or not
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Other than that+call screeening, this build is solid for an "experimental" build (Tbh they could have put the stable flag on this, but I assume they are waiting for bug reports before doing so). If anyone is looking for a good de-Googling solution, this is it.
Click to expand...
Click to collapse
Despite the hassle and increased expense, perhaps one of those Carplay AI boxes like Apple Pi might be the necessary workaround?
I'm very interested in this OS, but I too rely on carplay/auto as a general rule while driving. If I have to outsource my maps and music to an external box in order to have more comprehensive device security, that might just be the way it has to be.

Flippy125 said:
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Click to expand...
Click to collapse
Thank you for reporting. As curious as I am about this OS, this rules this out for me too. Been using AA for almost four years now and I'm hooked.

I want privacy, but I cannot live without syncing all my stuff together. Is this OS for me?