I YouTubed a couple of days ago and it seemed to work fine. I had to see what all the Miley Cyrus talk was all about.
I did the same thing. Lol. It was all crummy vidio so didn't get s good look at the camel toe.
Posted 29 August 2013 - 06:57 PM
I YouTubed a couple of days ago and it seemed to work fine. I had to see what all the Miley Cyrus talk was all about.
Posted 29 August 2013 - 07:14 PM
Will somebody post a link with the GAPPS they flashed with this rom? Thank you. Are GAPPS rom specific? i tried my Orion GAPPS and then i didnt have a AOSP keyboard but the system still booted normal and the GAPPS prompted as soon as it booted.... Thaks again.
I used the Slim GAPPs, you can find them on the Slim website. I think Orion is 4.2 and this is a 4.3 ROM. You need 4.3 GAPPs.
R. Long: Pixel 5
Posted 29 August 2013 - 08:17 PM
ok thank you. i was also told about goo.im. so i flashed the newest Gapps from there and they seem to be working good. but what sort of things are differant about Slim's? or are almost all Gapps the same.
Posted 29 August 2013 - 08:34 PM
ok thank you. i was also told about goo.im. so i flashed the newest Gapps from there and they seem to be working good. but what sort of things are differant about Slim's? or are almost all Gapps the same.
Thank Zoo/Owain for my Awesome Sig! If you want to support the Build Server that helps keep OSE going, Click HERE!
Posted 29 August 2013 - 09:01 PM
I'm not sure what's so confusing about it. Bam cut and copied the code, claimed it as their own, and didn't credit PAC. They also undermined them and released 4.3, with PAC's code, prior to PAC doing it. Yes, Android is all about kanging, but there's a difference between using a device tree/source and cutting/copying code. CK is just CM10.2, with some slight tweaks to it. If you build and port right, then kang all day long, but don't cut and copy, that's $#!+.
It's no coincidence that Tim is now the maintainer of PAC. First off, out of all the devs on XDA that posted Bam, he's the only one that took it down. That shows integrity. Second, BKJolly was involved in pulling Bam and he saw it as an opportunity to bring Tim into PAC's dev team. There's no conspiracy going on, and I wish people would drop the Bam discussion. It's over, it's done, it was a $#!+ situation, and people need to just drop it. If you want it back, port it yourself.
Posted 29 August 2013 - 09:42 PM
Posted 29 August 2013 - 09:56 PM
Posted 30 August 2013 - 03:11 PM
Hey what's up with that OSE ROM I found in the directories? It wouldn't flash. Something new?
Sent from my Droid RAZR M using Tapatalk 4
That may be the ROM that they've been trying to put together. If they get it finished, I'm sure it will knock our socks off.
R. Long: Pixel 5
Posted 30 August 2013 - 05:39 PM
Posted 31 August 2013 - 08:46 AM
Well, I finally ran into the issues that other people have been having. I thought I was safe, but 4.3 got me, some how. I'm still trying to dig into it. I loaded up the update from 8/29 and froze NFC. However, battery went from 60% to 5% in about 2hrs. I couldn't find the culprit, but I'm still working on it. When I tried to restore a backup, it would only flash system and boot.img, with no data. I'm not sure why this happened either, still digging into it. So, I reflashed TWRP and was able to restore fully after that. I guess I'm not always immune to these issues, but happily this was the first time it happened, and even better, it was easily resolved.
R. Long: Pixel 5
Posted 31 August 2013 - 08:56 AM
Well, I finally ran into the issues that other people have been having. I thought I was safe, but 4.3 got me, some how. I'm still trying to dig into it. I loaded up the update from 8/29 and froze NFC. However, battery went from 60% to 5% in about 2hrs. I couldn't find the culprit, but I'm still working on it. When I tried to restore a backup, it would only flash system and boot.img, with no data. I'm not sure why this happened either, still digging into it. So, I reflashed TWRP and was able to restore fully after that. I guess I'm not always immune to these issues, but happily this was the first time it happened, and even better, it was easily resolved.
Posted 31 August 2013 - 09:36 AM
Well, I finally ran into the issues that other people have been having. I thought I was safe, but 4.3 got me, some how. I'm still trying to dig into it. I loaded up the update from 8/29 and froze NFC. However, battery went from 60% to 5% in about 2hrs. I couldn't find the culprit, but I'm still working on it. When I tried to restore a backup, it would only flash system and boot.img, with no data. I'm not sure why this happened either, still digging into it. So, I reflashed TWRP and was able to restore fully after that. I guess I'm not always immune to these issues, but happily this was the first time it happened, and even better, it was easily resolved.
Same thing happened to me today. So does the 8/28 battery life better? And how 'bout the in-call sound on the 8/28?
Posted 31 August 2013 - 11:33 AM
8/28 had good battery and no issues with TWRP. Volume was low, but not enough to bother me.
R. Long: Pixel 5
Posted 31 August 2013 - 12:18 PM
Posted 31 August 2013 - 02:01 PM
Posted 31 August 2013 - 02:57 PM
Posted 31 August 2013 - 08:01 PM
8/28 volume almost made me deaf lol
Sent from my XT907 using Tapatalk 2
Now that you mention it, I was running 8/28 with Arrggh's kernel, I think that caused the volume issue.
R. Long: Pixel 5
Posted 01 September 2013 - 04:51 AM
Posted 01 September 2013 - 05:05 AM
Wtf. OK so titanium keeps telling me to turn on USB debugging like it always does. Only problem found no developer options to do so. Should be right next to apout phone.
Posted 01 September 2013 - 05:35 AM
Go into about phone and tap on the build number about 10 times
Sent from my XT907 using Tapatalk 2
0 members, 3 guests, 0 anonymous users