yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Olivierica:
Clash of the titan is not working in immersion mode but work when off. The double taping volume hey to toggle rotation lock is just another great treat from AOKP.

Respect. I am gonna start donating for all the good work

---------- Post added at 02:28 AM ---------- Previous post was at 02:22 AM ----------

Here you go Mike ?.

The ring is working fine for me in landscape mode. I dirty flash. Try to wipe dalvik and cache. And flash again latest nightly and gapps
[Nexus 7 (2013) Original Android Development] IS33D34DP30PL3:
Any reason why the 4.4 version of aokp is lacking all the features that 4.3 had?
[Nexus 7 (2013) Original Android Development] rpitera:
Hey, just got my first push for the new nightly. You weren't kidding about this app, I'm really happy I bought it. Thanks again.
[Nexus 7 (2013) Original Android Development] oadam11:
They have not added all the features in yet. They are starting with a stable base and then adding the custom aokp features that we all love.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] kingston73:
Anybody flash today's build yet? Any major changes?
[Nexus 7 (2013) Original Android Development] oadam11:
I'm flashing it now. Hopefully features are added to ROM control

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] niteh@wk:
I dirty flashed it last night over 1/9 build. No issues so far. Not much visible changes. Battery percent on status bar has been fixed (it was showing 0% in 1/9 build).
[Nexus 7 (2013) Original Android Development] sonofevil77:
I just flashed the latest nightly and this is a deal breaker for me. My app backups are on a SD card so until this is resolved I'm running clean lol. It's nice to be back on AOKP though woot!

Sent from my SCH-I605
[Nexus 7 (2013) Original Android Development] Jubomime:
Glitch.
[Nexus 7 (2013) Original Android Development] kingston73:
So stick mount isn't working on the 1/14 build? I just bought a microsd card reader but haven't gotten it yet, that's going to be sad if it won't work on this build. Guess I

L find out when it gets here.
[Nexus 7 (2013) Original Android Development] sonofevil77:
Correct, it just says busy or some crap lol. I switched over to aospal but I have Otg issues with that also. It reads but I can't write to SD. I have my SD reader in my Note now and it's writing fine. I keep going back to AICP 4.3 rom for the Otg reason.

Note 2 N3BULIZED!
[Nexus 7 (2013) Original Android Development] oadam11:
You can use an app called stickmount on the play store to mount SD cards

Sent from my Nexus 7 2013
[Nexus 7 (2013) Original Android Development] niteh@wk:
USB storage is not working in the new build. Even Stickmount keeps saying the device is busy.
[Nexus 7 (2013) Original Android Development] sonofevil77:
It's in stickmount that it says busy. Otg doesn't work on this build.

Note 2 N3BULIZED!
[Nexus 7 (2013) Original Android Development] gravedigger76:
Can you link this please, not really sure what / where this is. Not finding it on play store. -- Otg d9eant
[Nexus 7 (2013) Original Android Development] oadam11:
Here you go ?

https://play.google.com/store/apps/details?id=eu.chainfire.stickmount

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] gravedigger76:
Not stickmount. As you see above stickmount does Not work. My question was to the person that posted another I presume app bit may have misspelled the name as it's no where to be found.
[Nexus 7 (2013) Original Android Development] oadam11:
Oh. Sorry about that.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] kingston73:
Did USB storage work in the 1/9 build?
[Nexus 7 (2013) Original Android Development] hopscotchjunkie:
I assume he just misspelt "doesn't" (as in "otg doesn't work on this build" )
[Nexus 7 (2013) Original Android Development] o-o:
I'm guessing he meant "otg doesn't work", which isn't an app in the play store. otg = on the go
[Nexus 7 (2013) Original Android Development] sonofevil77:
Yes I meant doesn't lol. I have the long press setting on SwiftKey set to 200 ms so sometimes that happens lol.

Note 2 N3BULIZED!
[Nexus 7 (2013) Original Android Development] anko184:
Anyone tested otg with today's build?
[Nexus 7 (2013) Original Android Development] kingston73:
What build did it stop working? Or has it always been broken?
[Nexus 7 (2013) Original Android Development] anko184:
It was working on first builds and the last one was 2013-12-30.

BTW I just tested the latest build and it still needs the trick with otg helper to work.. ?

Στάλθηκε από το HTC One μου χρησιμοποιώντας Tapatalk
[Nexus 7 (2013) Original Android Development] sonofevil77:
+1 on this. I'm anxious for this one.

2013 N7 Kang Banged!
[Nexus 7 (2013) Original Android Development] niteh@wk:
otg is still not working on the 1/20 build the normal way. You can mount it using Otg Helper app (from PlayStore). It will fc, unmount it, Otg Helper will fc again. Now you can mount it using Stickmount. Inconvenient workaround but worked for me.
[Nexus 7 (2013) Original Android Development] kingston73:
Does that work around work consistently? Also, is this so you can read and write or does this just enable you to read the contents?
[Nexus 7 (2013) Original Android Development] niteh@wk:
It works consistently for me. It works until the next reboot, which you will need to do the OTG Helper workaround again. It enables both read and write. I tested it with a usb stick, fat32.

Edit: I forgot to mention I'm running with Elemental kernel, latest version with exFat support enabled. Haven't tested on stock kernel. Not sure if Elemental makes a diff.
[Nexus 7 (2013) Original Android Development] hyp3nitis:
can you install regular super user root app? I'm having problems with lucky patch and swype and titanium backup.

via galaxy noteII 4gLTE
[Nexus 7 (2013) Original Android Development] grifforama:
How do you stop the Google search ring from doing this in landscape?
[Nexus 7 (2013) Original Android Development] unknownyello:
Yes you can
[Nexus 7 (2013) Original Android Development] ricostuart:
Anyone know how to fix the search ring when in landscape mode?
[Nexus 7 (2013) Original Android Development] grifforama:
+1

---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------

This is actually a bug within AOKP and needs to be fixed. Other ROM's do not have this problem.

The problem persists in the latest build (01/25)
[Nexus 7 (2013) Original Android Development] niteh@wk:
Fixed in latest build, 2014-2-1.
[Nexus 7 (2013) Original Android Development] Olivierica:
kernel

Latest update brought the full screen mode working with games. Awesome.

Can anyone recomand me a way of getting sweep2wake with my AOKP experience?
[Nexus 7 (2013) Original Android Development] oadam11:
Try flashing a custom kernal such as elemental x

Sent from my Nexus 7 2013
[Nexus 7 (2013) Original Android Development] arby80:
The rom does not recognize that it is charging on a qi charger properly when the battery is full , and therefore will not turn the screen on and launch daydream. Although qi charging is way faster on aokp kit kat. I hope they will get around to correcting this.
[Nexus 7 (2013) Original Android Development] silver04v:
On the latest nightly and running smooth. Good old AOKP
[Nexus 7 (2013) Original Android Development] rubyman94:
Love this rom ?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Of course you do, you own an iPhone :p
[Nexus 7 (2013) Original Android Development] georgiapi:
New Nexus 7 2013 WiFi Owner Checking In

Picked up a new 32GB unit @ Walmart today. Ship to store ready 20 minutes after checking out. $262.00.

Battery was @ 50%. All appearances indicated it be a brand new spanker.

As soon as it WiFi connected it upgraded to KK KOT49H without a hitch.

Just wanted to check in before flashing and bashing to see if there is anything wrong with my workflow.

I am going to use Wugfresh unlock & root because I have been away from the cmd thing for a while.

I see he only provides TRWP Is there no support for CWM?

Thanks!
[Nexus 7 (2013) Original Android Development] oadam11:
You can flash cwn after you used wugfresh.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] georgiapi:
WoW, What a frightening experience.

I have used cmd prompt method with rooting before. I used DOS on computers before windows was released. Heh! Thats how old I am.

But with my Galaxy Nexus, between Wug's and Skipsoft's kits I have been spoiled and lazy.

So I tried The Wug's kit today got to a point of driver difficulties and device recognition and then switched to Skipsoft's kit and finally a dead brick that would not respond to button pushes, USB connections. Argh! My new Baby!

I did everything very carefully and methodically. I build my own computers and know better then to guess or get hasty. I did all the driver uninstalls and deletions in the troubleshooting guides, you name it I did it.

So............ sitting here with a brick I connected it again and started Wugs kit and chose the Current Status "Soft-Bricked/Bootloop" option and chose the "Flash Stock + Unroot button and a few seconds later - BAM! She's Alive! The Google unlock screen shows up and she boots, and she is rooted!

WTF!

She is running fine and I have AOKP's latest nightly on it.

All the time it took to fight that I could have done it manually.
[Nexus 7 (2013) Original Android Development] boomerod:
Lockscreen Ribbon

Can't seem to get the icons to recognize my touch. Ribbon seems to be too close to the unlock orb so that each time I try an icon I get the orb emanation animation.

Also, since above was not working for me, tried ring shortcuts, but they don't show up on the lockscreen - just the desktop.
[Nexus 7 (2013) Original Android Development] Nbsss:
Has anyone ported aokp swipe ribbons to xposed framework or as a standalone app?
[Nexus 7 (2013) Original Android Development] Moudii:
There is a new nightly up btw.. ☺
[Nexus 7 (2013) Original Android Development] niteh@wk:
Is this version of AOKP for flo non-caf? I flashed caf version of elementalx kernel and my N7 won't boot. Flashed the aosp/non-caf version and it worked fine. On my N5 phone however I had to flash the caf version of the kernel... Both the N7 and N5 are running the latest AOKP nightly. Confused [emoji10]
[Nexus 7 (2013) Original Android Development] guyd:
N5 is using CAF, but N7 is AOSP.
[Nexus 7 (2013) Original Android Development] toebee76:
Does anyone else have the issue of no sound when trying to use a slimport? It seems to be isolated to aokp. If so does anyone know of a fix?
[Nexus 7 (2013) Original Android Development] sonofevil77:
Is Otg working yet?

Note 3 Pimp Slapped
[Nexus 7 (2013) Original Android Development] Moudii:
Got no sound from slimport.. No otg cable atm.
[Nexus 7 (2013) Original Android Development] arby80:
I also have no sound with swiftkey, it is isolated to the latest nightly and the nexus 7. Sound still works with swiftkey on my nexus 5 and the previous build on my nexus 7.
[Nexus 7 (2013) Original Android Development] burizon:
Volume rocker not wake up. I am on the latest version of your ROM. What should I try to do?
[Nexus 7 (2013) Original Android Development] niteh@wk:
Did you enable it in ROM Control? Mine wakes up fine using volume rocker.
[Nexus 7 (2013) Original Android Development] burizon:
Yes, I did. Could it be that some installed application interferes with this feature?

Sent from i9250 / AOKP ROM
[Nexus 7 (2013) Original Android Development] Moudii:
Working with the latest nightly for me. So is everything else, for now, only been playing around for a few hours with it tho.
[Nexus 7 (2013) Original Android Development] Migamix:
well... I hate to be that guy...

I used to live and breathe AOKP on my Gnex, and even a little on my newer devices... back before the CM core change over. there was a reason I went back and stuck to AOSP builds. stability. so. I got brave the other day and put the latest build on my N7.2 only as I need at least my phone in peak working order over the next few days. turns out I needed my tablet in peak order too. heavy tech week for me. well. no good for me. the tablet decided it was going to become unresponsive and hot boot on me several times throughout the day at the most vital times. this is something I have repeatedly gotten with CM installs. in not going to place blame. but I'm so saddened that AOKP is not my crack flash anymore. maybe if the decision to go back to AOSP builds, we could work this out.

yeah, I'm sure I'll try again every once in a while, but this was the first AOKP I've flashed in almost 6 months. I sighed (after yelling WTF) at an extremely critical time (on top of a tall ladder) and had to do a previous working nandroid back to an AOSP ROM I had no problems with to complete my job , while still up on the ladder.

let me know when you guys go back to AOSP, the CAF crap is not worth it.

sorry, and thanks for the crack in those good old days.

don't bother asking for a logcat. hardly in a position to pull logs at that point.

it's CM, not you.

-typing like i think i know something on my N5-
[Nexus 7 (2013) Original Android Development] niteh@wk:
The risks you accept to take when flashing a custom ROM. If everyone else is not experiencing the issue you have, there gotta be something on your device that's causing it. Custom kernel, misconfiguration, defective hardware...
[Nexus 7 (2013) Original Android Development] quickdraw86:
If perfectly working devices are that mission-critical for you, installing beta software on them just isn't a good idea. The expectation of a bug-free experience on nightlies, weeklies, etc. isn't realistic, no matter the talent of the devs. involved. Look to stable, milestone, or even stock builds if you need stable, crackflashing nightly, or automated builds comes with no guarantees...
[Nexus 7 (2013) Original Android Development] Migamix:
slimroms runs on the same idea. its all beta and nightlies , yet as other AOSP based builds ive used in recent times on several devices..have been a reliable, stable , nolag, not hot boot ridden mess that all CM based roms have become... problem is, if my whole post statement was not read, i stated roughly that CM is getting very sloppy. and apparently everyone is pulling from that sloppy non snapshot base (instead of something theoretically more stable) then they are building stuff off of that.. or that's how every CM based ROM seems to be heading. why bother modifying any of CMs. you build a jaguar frame around a ford pinto, its still a crappy car.

CM guys need to take a huge step back, and focus on the grand fixes. but what's the pont, we will see the next google release soon, and Dev for 444 will stop, with its current bugs. while CM teams begin to ravage whatever we get in October.

my post, since it seems to not have been read no matter how light hearted I tried to type it, flatly states that I'm in the camp where I think CM just plain sucks now (it was a gradual decline really showing its face about 4 months ago). and while I lived on AOKP for ages.. I was let down by the unstable crappyness of its CM core.

they work hard on the ROM, I understand. but team kang is trying to put shiny gold paint on a turd of a code base.

as for flashing a milestone. fine and dandy if I want jelly bean.. milestone one, all the way back in December for flo (nothing found or available for hammerhead or toro that's listed as KitKat). bit out of date don't you think?

now.. do you want me to be a fanboi, or be honest and call it like I see it. I posted politely. but sometimes I have to lace up my boots tight and stomp my way around.. being honest would have kept jar jar out of my childhood movie world.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Slim has stable builds for devices on its site, AOKP does indeed not have stable for all devices though.
[Nexus 7 (2013) Original Android Development] flyinion:
Yeah I think I'm in the same situation. I finally got around to putting my first ROM on my 2013 N7 and went with AOKP since I'd used them forever on my GNex. Within a week I had to revert to stock rooted because we were going on a cruise a few weeks ago and I bought a couple movies for the first time off Google Play and quickly found out I could not play them on AOKP if they were set to download to device instead of stream. The whole reason for buying them was to stream offline on the airplane or on the ship outside of cell service. As near as I can tell though this is an issue with any custom ROM so I guess I'm just out of luck for running one on my N7.
[Nexus 7 (2013) Original Android Development] Spyrious:
Is the gps working on this?Thanks
[Nexus 7 (2013) Original Android Development] beany>:
If you have space use MultiROM and have the option of both stock and a ROM or ROMs of your choice.
[Nexus 7 (2013) Original Android Development] Protonus:
Edit: nm
[Nexus 7 (2013) Original Android Development] Rickymax:
what kernel may i use in this rom to UC the cores? i cant with the stock.
[Nexus 7 (2013) Original Android Development] quickdraw86:
Just about any current AOSP based third party kernel... Elemental x, glitch... Etc. you may need an app like trickstermod in order to toggle all of the parameters of a third party kernel though...
[Nexus 7 (2013) Original Android Development] Sindee75:
[MENTION=4357706]rohan32[/MENTION] this thread is old. I hope I can find help. My nexus 7 2013 was on jelly bean 4.4.4 due to a downgrade from issues with 6.01. Factory images will not allow me to upgrade, freezes on boot animation. So I went back to 4.4.4 but tons of google play and services errors. Apks would not help. So, I installed your aokp Rom for 4.4. It booted up. Tried to install several gapps all with error code 20. So, I upgraded to your latest nugout and installed gapps Pico all installed via trwp with no errors. Now, I am stuck on your boot animation screen. Did cache and delvacke wipes. No help. Can someone help me please? I don't know how to get past the boot animation screen. Googled this issue for a week and tried various things. Nothing is helping. Hope someone here can help? Thanks, Cindy
[Nexus 7 (2013) Original Android Development] quickdraw86:
Error code 20 in TWRP means that you tried to install a gapps that was an inappropriate version for the ROM you installed. No one else has your device. State your exact steps and exact versions for further assistance.
[Nexus 7 (2013) Original Android Development] Sindee75:
I thought I explained exactly what steps I took above?

I tried Pico gaps, nano gaps and mini gaps on 4.4.4 of your version. All gave an error code of 20 in twrp.

Which gapps should I use for 4.4.4?

I then upgraded to your latest, 7.0.1? All installed with no errors but stuck in boot animation screen. How can I fix this please? Or, get gapps working in 4.4.4?

Thank you....
[Nexus 7 (2013) Original Android Development] quickdraw86:
Not my rom...

Gapps packages aren't universal across all versions of android. Your gapps package must both match the android version of the custom ROM, and, on later versions of Android for this device, m, n, etc., must be able to fit in the /system partition with the ROM. For example, a 4.4.4 rom requires 4.4.4 gapps.

I would check your installed version of TWRP. The latest TWRP may or may not boot much older roms.

You don't need to use a toolkit if you have TWRP successfully installed.

Wipe everything besides internal storage in TWRP's wipe menu. Install the ROM and an appropriate gapps as a batch in the same recovery session. Reboot. If that still results in a bootloop, check the md5 or sha1 hashes for your downloaded rom and gapps. If your hashes match, collect logs if possible, or revert to a stock image.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Already merged. Next official nightly will have it :)
[Nexus 7 (2013) Original Android Development] mountainloafers:
Word!

Let it flo...
[Nexus 7 (2013) Original Android Development] ziantic:
Haha, gotta love the porn unicorn :p
[Nexus 7 (2013) Original Android Development] NekroWolfen:
You can feel the unicorn magic with this ROM :)

Was my #1 choice with the Nexus(2012) and still my #1 choice with this Nexus, can't wait for the next updates.
[Nexus 7 (2013) Original Android Development] ziantic:
Pardon me but does AOKP has the OTA update system ? I'm looking forward to have OTA updates very much.
[Nexus 7 (2013) Original Android Development] creeve4:
Why does AOKP base this off CM source instead of AOSP? Why base use CM source for any nexus device when AOSP has everything we need without the bugs of CM?
[Nexus 7 (2013) Original Android Development] ziantic:
I thought many of AOKP roms based on CM, because CM is like a base for chefs. AOSP is kinda raw, but CM 10.2 on the Nexus is okay, everything works fine.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
How did you both come to the conclusion that it is cm based?

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] ziantic:
I saw the Cyanogenmod Enabled ... maybe it's just some features but AOKP is not based on CM, my bad.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Alright. That means the device/kernel repositories have been forked from cm, meaning the device has been "enabled" with the help of cm. Aokp is and never will be based off cm, like the guy(or you?) above said, why do we need cm when there's aosp support for our devices? Hope this cleared your doubts. :)

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] creeve4:
Thanks for the clarification. But why even fork from CM if we have AOSP? Please forgive my ignorance, I'm just trying to understand.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
I'm sorry, that is something you have to ask the aokp devs. This is all i know :)

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] five40:
Is the option to change LCD density in this ROM or do I need a 3rd party app?

Thanks
[Nexus 7 (2013) Original Android Development] creeve4:
The USB fast charge toggle does not work, the toggle does not change state when activated. I'm using franco kernel r3. Is anyone experiencing this?
[Nexus 7 (2013) Original Android Development] greogory:
Yes, same problem for me with the default 3.4.0-gcee7856 kernel.

The swagger toggle doesn't seem to work either, but since I have no idea what it does in the 1st place, I can't exactly say what it's not doing. Well, besides not doing anything, I mean. :)
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Swagger does nothing. :) it's just a tease.
[Nexus 7 (2013) Original Android Development] greogory:
I stand corrected. The swagger toggle works perfectly as designed. :beer:
[Nexus 7 (2013) Original Android Development] catlog:
Doesn't work for me neither and I'm not using another kernel. Also, linking the main volume and notification volume doesn't seem to work if that's what Link volumes and Link mute states were supposed to do.

Aside from that, the ROM seems smooth and solid.
[Nexus 7 (2013) Original Android Development] mrRobinson:
Whoa, whoa... That swagger toggle uses the pink unicorn magic to give you swagger. I mean, c'mon, let's not promote blasphemy.

Simple user error if you don't feel the added swagger. :angel:
[Nexus 7 (2013) Original Android Development] NekroWolfen:
Can someone please confirm that the latest nightly is in fact the sep/28? That there hasn't been another one.
[Nexus 7 (2013) Original Android Development] catlog:
As far as I know, that's the latest official nightly. I could be wrong though.
[Nexus 7 (2013) Original Android Development] creeve4:
When can we expect to see a move away from using CAF/CM source for the kernel? Let's get back to AOSP please.
[Nexus 7 (2013) Original Android Development] ktkr:
Same here, it will be great to have AOSP compatibility back.