yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] BLADESMAN1889:
I'm assuming it's to free up RAM ?

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] LarsenB:
Edit

Is 'anyones' N4 short of ram?! :banghead:

'MOST' recents are suspended and use nothing. It's a pointless exercise.

Simmer down. ↓
[Nexus 4 Original Android Development] BLADESMAN1889:
NB, I thought I recognized the rude in yer face style of post, you were the reason the UK N⁴ thread was getting cleaned by the Mods :eek:

Did I say that 'I' was short of RAM - no I did not :banghead: :banghead:

When Recents is selected a list of apps appear with RAM bar at the top of the page showing Used & Free & a Kill All button at the bottom.

When apps are swiped away OR the Kill All is used, guess what 'appears' to happen ?

Correct - the Free RAM Increases (rightly or wrongly) :eek:

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] MontAlbert:
anyone else having issues where the right swipe ribbon stops working? I have found only a reboot fixes it to get it working again. Can't figure out why it stops working, just doesn't. even going into rom control and saving it again doesn't start it again.
[Nexus 4 Original Android Development] orihuri:
I have no problem at all with ribbons.im using the left and the right and im on the last nightly..I always do clean installs and honestly I haven't encountered any fc in ages.
[Nexus 4 Original Android Development] ChanceOfChange:
when u press the recent menu at exit you can see the a static wallpaper to moved up and down fast some element on it.. so so so hard to explain m8!
[Nexus 4 Original Android Development] Joloxx9:
Milestone 1 is the latest build , am I right?

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] ChanceOfChange:
latest kinda stable build
[Nexus 4 Original Android Development] BLADESMAN1889:
Yes I have had the left swipe ribbon stop working with a reboot the only fix.

It has only happened the once.

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​

---------- Post added at 03:13 PM ---------- Previous post was at 03:06 PM ----------

Oh I think I understand but as yet I've not had this happen but I will make a note & keep an eye on it.

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] ChanceOfChange:
that will be awsome to do it for me m8! cause i cant use aokp for some bugs that have still and this very anoying staff! modded stock by me work tho flawlessly!
[Nexus 4 Original Android Development] ermacwins:
Wiped data, flashed mr1 and stuck on bootlogo for 5 mins now
[Nexus 4 Original Android Development] Joel Chan:
That shouldn't be happening. Perhaps you could wipe once more?
[Nexus 4 Original Android Development] ermacwins:
Already tried that
[Nexus 4 Original Android Development] Bluewall:
Sounds like a bad download to me then
[Nexus 4 Original Android Development] ermacwins:
Whats worse is that my nandroid restore has failed so Im stuck on a black screen and cant get another rom on the storage
[Nexus 4 Original Android Development] cantevencode:
Which build are you running? Most recent apps problems were

fixed just after milestone 1 so a nightly might fix it

Could try adb push or sideload
[Nexus 4 Original Android Development] ermacwins:
Havent dont that before. How?
[Nexus 4 Original Android Development] dankoman:
http://www.xda-developers.com/android/adb-easy-tutorial/
[Nexus 4 Original Android Development] Mercado_Negro:
Connect your device via USB

Make sure it's detected by typing "adb devices"

Then, in recovery, type, for example "adb push aokp_mako_nightly_2013-04-30.zip /sdcard/
[Nexus 4 Original Android Development] ChanceOfChange:
i first start using milestone and then all nightlys so far...the problem still excists!
[Nexus 4 Original Android Development] ceejay83:
I don't have this problem. I know they fixed recent menu bugs in the latest nightlies, try them out
[Nexus 4 Original Android Development] ermacwins:
It detected the device, after about 40 seconds it said failed.

C:\Users\x\Desktop\adb>adb push cm-10.1-20130501-NIGHTLY-mako.zip /sdcard

failed to copy 'cm-10.1-20130501-NIGHTLY-mako.zip' to '/sdcard/cm-10.1-20130501-

NIGHTLY-mako.zip': Read-only file system

C:\Users\x\Desktop\adb>
[Nexus 4 Original Android Development] Mercado_Negro:
Are you sure it is mounted and writable?
[Nexus 4 Original Android Development] ermacwins:
Well im in twrp and in mount it has data and cache as checked but it doesnt let me mount system...
[Nexus 4 Original Android Development] phonepersonality:
A couple of things...

1. This appears to be a CM10 ROM build you're pushing to your device, not AOKP.

2. The new version of ADB has new security features built-in. Depending on how your phone was configured prior to the failed ROM flash; that may be a reason why your file system is detected as read-only.

It could also be that USB debugging isn't enabled on the phone and maybe (keep me honest here folks) your phone has lost it's root somehow.

Now possible solutions (because I hate presenting only problems) -

1. If your phone was already running a custom ROM, you could try re-flashing that (hopefully, you still have it saved on your phone) and then attempt to restore your data from your Nandroid back-up.

You mentioned the back-up failed, but you didn't say what caused the failure. If it's an MD5 Checksum error, there are workarounds.

2. Flash SU root to your phone and then attempt ADB push again. You may wanna attempt a new AOKP (or whatever) ROM and do an MD5 look-up to ensure the checksums match prior to flashing.

3. There was something else, but I've forgotten. Listening to the news about the Boston bomber additional arrests...gimme a second. It'll come back to me...
[Nexus 4 Original Android Development] ermacwins:
1. Chose cm because aokp failed in the first place

2. Not sure if debugging was enabled

1. Trying to reflash same rom it says failed right out the bat

2. Might try su

Before I flashed the rom I updated twrp from 2.4.3.0 to 2.5 now going back to 2.4 the resore works but stuck on logo. Roms flashes still fail

Im thinking might need to flash stock image? If so, will it wipe the storage?
[Nexus 4 Original Android Development] phonepersonality:
Stock image probably not necessary.

If the restore worked and you're stuck on the boot logo, then something else is up.

Was it a full restore/back-up i.e. system, boot and data, or did you uncheck some items during the back up?

What were you running before you flashed AOKP? Was it a custom ROM or stock?

If not stock, try flashing the custom ROM but don't flash GAPPS just yet. Wipe your caches and reboot and see if the ROM boots up.

EDIT - To answer your question, no. I'm pretty sure the only flash that will wipe your data partition by default is a Bootloader flash.
[Nexus 4 Original Android Development] Mercado_Negro:
It won't wipe it if you don't flash the userdata image. At least that's what papers say. Try flashing the system image first and see if it boots. If it does, make a backup of your data and then flash all the images again from the bootloader just to be sure you'll be starting fresh on your next ROM flash.
[Nexus 4 Original Android Development] cantevencode:
Yeah, unfortunately it will wipe the storage. I know you can restore app data from adb backups if you have the pro version of titanium backup but I'm not sure what you can do about other data though
[Nexus 4 Original Android Development] ermacwins:
Yes it was a full restore.

Was running a cm nightly prior to the fiasco. I have been flashing without gapp as well but no luck.

I changed to cwm and when I flash the same cm nightly it says bad and aborts but flashes the aokp rom fine which then gets stuck in boot logo
[Nexus 4 Original Android Development] ceejay83:
It's probably a bad download, did you check the md5?
[Nexus 4 Original Android Development] Mercado_Negro:
Like I said, flash the system image and wipe dalvik/cache, then boot. In the factory occam images there are six images, flash system.img.
[Nexus 4 Original Android Development] ermacwins:
Just did that and its still stuck. Cant afford to lose files from my storage. I will try Paranoid rom and if that doesnt work, then will flash factory image
[Nexus 4 Original Android Development] pkelly517:
You might also want to try flashing the stock boot image and recovery before you go full on factory image.

System, boot and recovery.

Don't flash the userdata.
[Nexus 4 Original Android Development] Mercado_Negro:
Which factory image? This is how I've always reverted to full stock:

Put all six images in my adb folder /platform-tools (where fastboot is)

Boot into bootloader and then flash each image, one by one:

fastboot flash bootloader nameofbootloader.img

fastboot reboot-bootloader

fastboot flash radio nameofradio.img

fastboot flash reboot-bootloader

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

Then I move to recovery and holding power and volume up I access to the stock recovery options. Then wipe dalvik/cache and then wipe cache (phone restarts automatically at this point).

That's why I'm asking which factory image you're going to flash because these are all factory images of different partitions.
[Nexus 4 Original Android Development] ceejay83:
this is why i always have a nandroid, and an older rom that i previously used so i know it boots.
[Nexus 4 Original Android Development] spaceman860:
You can skip the userdata.IMG so you don't lose sdcard stuff

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
Exactly :)
[Nexus 4 Original Android Development] ermacwins:
Im using occam-jdq39 did all steps except userdata.img

volume up plus power, stuck at logo. Volume down plus power shows android but option to wipe anything

currently stuck at google logo
[Nexus 4 Original Android Development] Mercado_Negro:
An android laying on its back (or front, can't remember right now) with a red triangle? That's the stock recovery. Press and hold power button and then press volume up one time. That'll show you those options I mentioned above. Wipe dalvik/cache AND cache.

[EDIT] These are the options I'm talking about: http://cdn.androidpolice.com/wp-content/uploads/2012/10/nexusae0_wm_IMG_20121009_124737.jpg
[Nexus 4 Original Android Development] ermacwins:
Volume up just takes me google logo. Volume down takes me to Android on his back but no wipe options
[Nexus 4 Original Android Development] ceejay83:
Can you make a thread in Q&A or PMs? Thread is derailed
[Nexus 4 Original Android Development] Mercado_Negro:
That's correct. The thing is you have press and hold power and press volume up one time WHEN you're seeing the Android laying on his back. You won't see those options until you see the Android and do the press/hold/press sequence.

---------- Post added at 04:15 PM ---------- Previous post was at 04:09 PM ----------

Hopefully someone will read this in the future and learn something. I really don't understand why everybody is like this here on xda. I'm a moderator on 5 audio forums and the motto is always the same: help and try to solve, no matter what. I've seen more off-topic discussions around here that actually don't have anything to do with Android. This is related to our system.

Anyways... Yes, please let's take this to PMs, ermacwins.
[Nexus 4 Original Android Development] ermacwins:
Thanks for all the help it worked. On the downside my storage got formatted, dont know what caused that
[Nexus 4 Original Android Development] Mercado_Negro:
Oh... Now that you mention it I know why :( the first option in the stock recovery is "wipe DATA/dalvik", not "wipe dalvik/cache"... Sorry about that :( ... Now I see there's no way to keep the data partition intact, even without flashing the userdata image. I'm really sorry :(
[Nexus 4 Original Android Development] ermacwins:
No probs, cant do anything about it, lost Titanium back files and other stuff.

Do you think after doing all the steps you mentioned then instead of going stock recovery, flash custom recovery and wipe data, would that have worked in not formatting storage?

And is there no way of accessing the storage from recovery?
[Nexus 4 Original Android Development] Mercado_Negro:
Since you've already solved your problem, could we please take this to PMs? I wouldn't like to derail this thread anymore :)
[Nexus 4 Original Android Development] spaceman860:
Check your pm

Sent from my Nexus 4
[Nexus 4 Original Android Development] andy_rose:
OK flashed latest nightly (30.04) and noticed a new setting I've never seen before.

Under rom control-system there is something called Installer. What is that exactly?

I noticed one of the options is persist host file.

If I wanna install Adaway, do that option keep adaway from changing my host file?

Have I understood it right?

Sent from my Nexus 4
[Nexus 4 Original Android Development] BLADESMAN1889:
Though you are completely right - the guy was in a real fix & at that particular point in time shifting over & starting a new thread would have just been like getting kicked in the balls :eek:

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] ceejay83:
No it keeps the hosts file preserved when you dirty flash an update.
[Nexus 4 Original Android Development] ermacwins:
Thanks for the help dude but all sorted it now with except the loss of data
[Nexus 4 Original Android Development] alexchin91:
Can i flash on top on my stock 4.2.2 rom without wiping my data?
[Nexus 4 Original Android Development] ChanceOfChange:
clean methood is always the best stable one! even with a uncompleted rom yet still more to come!
[Nexus 4 Original Android Development] zakkyzombie:
Did you uhm..flash gapps? :o
[Nexus 4 Original Android Development] Goku80:
guys what is ribbon suppose to do?
[Nexus 4 Original Android Development] kenypowa:
There is a kill all button.
[Nexus 4 Original Android Development] Jubakuba:
https://www.youtube.com/watch?v=T7HdeboOEFI&list=UUAYEo8n0XPHYG5By90_TNxg&index=14

Couple more options than this now.
[Nexus 4 Original Android Development] JS0724:
Using default keyboard. Words in personal dictionary are not being recognized and are being auto corrected. In settings I can see they are still there. Suggestions?
[Nexus 4 Original Android Development] Savant:
Force close, clear data reboot and see if it fixes your issue. The bad it'll delete your personal dictionary .
[Nexus 4 Original Android Development] big70tom:
Lil help. I love AOKP. only thing at all I miss is DSP manager and Apollo. Can I flash these to this ROM? If not what is my best avenue to pursue for music? I work graveyards and have my Ajay's headphones on all night
[Nexus 4 Original Android Development] Savant:
Yes you can use it and I would just flash the xlouder mod by misledz . http://xdaforums.com/showthread.php... [01/05/13] JB Louder Audio Improvement Patch
[Nexus 4 Original Android Development] apatal:
Try this: go to your personal dictionary list of words. Click on any word so that you go to the edit window now just press back to the list. Now click on the old plus sign at the top so you can add a new word to the dictionary, but then press back until you exit settings. Try typing again and see if your personal dictionary is now recognized. Hope this helps. :)
[Nexus 4 Original Android Development] apatal:
Hi guys, just curious. By deleting 73-gapps-mako.sh fron the addon.d folder, will I get the AOKP camera everytime I flash the ROM + Gapps, or should I skip Gapps?
[Nexus 4 Original Android Development] ceejay83:
you can just use the banks gapps package that doesn't have the photosphere camera included
[Nexus 4 Original Android Development] tmdo:
anyone having problems with the recent apps graphic glitch. do not have superSU or busybox installed or updated from the google play app. aokp has a problem with one or either of these install or updated.

i had this problem when i was using the WugFresh Root Toolkit to Root the phone. it would install superSU and busybox and when i tried to install aokp it would mess up my recent apps.

what i did to fix this was Flash Stock then used the advanced utilities in wugfesh toolkit to flash a recovery img of TWRP. then manually installed aokp and gapps from TWRP. dont bother installing supersu or busybox from google play.
[Nexus 4 Original Android Development] ceejay83:
aokp already comes with busybox and superuser. why would you install them again?
[Nexus 4 Original Android Development] tmdo:
because wugfresh installs them automatically when you root.
[Nexus 4 Original Android Development] ceejay83:
You don't need to root if you're going to flash aokp because it's already rooted LOL. You only need to flash a custom recovery
[Nexus 4 Original Android Development] tmdo:
i'm not telling people to root. i'm telling them to bypass the Root option in the Toolkit by flashing TWRP to recovery and then installing aokp....

learn to read mate.

only reason i was rooting before installing aokp was so i could install using goomanager
[Nexus 4 Original Android Development] hello247:
New nightly is out. :)

goo.im/devs/aokp/mako/nightly

Swyped using Nexus 4
[Nexus 4 Original Android Development] idle0095:
Anyone know if the new PA Halo could come to AOKP?
[Nexus 4 Original Android Development] ceejay83:
they'll possibly add something similar to it, but aokp has never included PA features
[Nexus 4 Original Android Development] JS0724:
Worked like a charm. Thanks!
[Nexus 4 Original Android Development] forgettolive:
i got wifi auto disconnect on aokp 20130430 so anything new for aokp 20130503?
[Nexus 4 Original Android Development] toanau:
Is this the same white hawk nightly
[Nexus 4 Original Android Development] forgettolive:
have just flash new version. hope everything ok with wifi connect
[Nexus 4 Original Android Development] Jubakuba:
Seems cornerstone made the rounds to all the larger teams again...which brought up "no, to that...but..." for a few.

A couple guys are thinking it out. We may have an app-in-app sort thing someday, but it won't be this.
[Nexus 4 Original Android Development] forgettolive:
i think they want to make difference

but that is not usefull for user ^^
[Nexus 4 Original Android Development] Emama:
Is the Halo means the same thing of Facebook chat head?

I want it for sms or any msg IM+ once I saw this on FB msg, this is really cool
[Nexus 4 Original Android Development] gagdude:
Basically, but a little more advanced.

Check out PA's Google+ page for a video
[Nexus 4 Original Android Development] drawde40599:
AOKPUSH swagger :D bout freaking time :P
[Nexus 4 Original Android Development] hello247:
No this is the official aokp nightly

Swyped using Nexus 4
[Nexus 4 Original Android Development] apatal:
Hi guys, just noticed I can't switch off HDR mode in the AOKP camera after I turned it on. Can someone confirm this please? Thanks.
[Nexus 4 Original Android Development] hello247:
No issues here.

Swyped using Nexus 4
[Nexus 4 Original Android Development] phonepersonality:
To disable off HDR mode, reselect HDR from the menu wheel.
[Nexus 4 Original Android Development] apatal:
Yeah I know how, somehow, it wasn't changing back to normal mode for me. Must just be a derp. Nevermind, I'll disrty flash another version. Thanks! :)
[Nexus 4 Original Android Development] toanau:
I know this has been ask before. But what is the difference between the white hawk and the official nightly
[Nexus 4 Original Android Development] phonepersonality:
I was just gonna suggest reflashing the AOKP camera or GAPPS :)

All the best.
[Nexus 4 Original Android Development] ceejay83:
They're both pretty similar, white hawk will have some cherry picks

If you know it's been asked before, try searching
[Nexus 4 Original Android Development] Lownita:
Is aokp based on cm or aosp? I guess it was cm?
[Nexus 4 Original Android Development] ceejay83:
based on aosp and it has some cm cherry picks
[Nexus 4 Original Android Development] apatal:
Wait...what?! :eek:
[Nexus 4 Original Android Development] VaksenDK:
Are you sure about that?

To my knowledge official aokp is 100% based on aosp and everything extra is written from ground, and it does not contain a single line of cm code. Which also explains why aokp runs just that bit smoother than cm and cm based roms.

Although some functions and ideas may be inspired by cm (and visa versa).
[Nexus 4 Original Android Development] VaksenDK:
Double post, sorry.
[Nexus 4 Original Android Development] Emama:
quick question:

No picasa sync nor photosphere if using AOKP camera, right?
[Nexus 4 Original Android Development] BLADESMAN1889:
& also why it is in the Original Android Dev section :)

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------

Def no photosphere

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] nbeebe24:
Not true. AOKP does pick some code from cm.
[Nexus 4 Original Android Development] Romanbb:
Of course AOKP has code from CM. Why wouldn't it?

There's no such thing as 100% from scratch with ROMs last I heard :)
[Nexus 4 Original Android Development] JaylanPHNX:
Yeah, if nothing else, bug fixes get shared all the time.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] ceejay83:
There's many aosp roms in the original android dev section that have cherry picks from all over the place.

---------- Post added at 06:03 PM ---------- Previous post was at 05:12 PM ----------

People forget what the K stands for in AOKP :p
[Nexus 4 Original Android Development] Romanbb:
Isn't it ironic?
[Nexus 4 Original Android Development] zelendel:
You are mistaken on this. Alot of AOKP coding is built off of CM coding.
[Nexus 4 Original Android Development] nbeebe24:
How am I mistaken? I said aokp does use cm code
[Nexus 4 Original Android Development] zelendel:
Sorry quoted the wrong post.
[Nexus 4 Original Android Development] Semantics:
Anyone having the issue of when opening the messaging app, the keyboard wont work until you back out of the app and re-open it? This happens with both the Android keyboard, and Swiftkey. Its been going on since r6 and milestone 1.
[Nexus 4 Original Android Development] Mercado_Negro:
I can't confirm that here with Swiftkey.
[Nexus 4 Original Android Development] forgettolive:
everything ok with me. using milestone 1 and swiftkey :laugh:
[Nexus 4 Original Android Development] drawde40599:
Works fine here, both those keyboards
[Nexus 4 Original Android Development] Mercado_Negro:
Apparently these AOKP builds have problems with BaNks GApps, not sure why. I was having problems with TiBu so I decided to revert to Stock. After this, I tried to flash M1 (just to start with it, I'd flash the lastest nightly right after that), and BaNks GApps but I couldn't get past the "X" logo. Then I wiped everything and tried the latest nightly: same thing. Then I tried it with the official gapps and it worked. I wonder what the problem is.
[Nexus 4 Original Android Development] zakkyzombie:
Could someone point me to the latest, most stable nightly?

NEXUS⁴
[Nexus 4 Original Android Development] deani77:
But in my case with last Whitehawkx built, everything work as normal with banks gapps.

Sent from my AOKP N4
[Nexus 4 Original Android Development] Mercado_Negro:
Sure: http://goo.im/devs/aokp/mako/nightly/aokp_mako_nightly_2013-05-03.zip

---------- Post added at 02:56 AM ---------- Previous post was at 02:53 AM ----------

Yeah, there's something weird on my end. I just reverted to stock, just to try, and tried to flash PA 26/april build and I'm still waiting for it, stuck in the boot logo. This is really weird. I'm not doing anything different here, I've done this a lot....

Thanks for checking :)

[EDIT] I think I found the problem. I wasn't wiping data before flashing. It's weird that it worked correctly with the official gapps... anyways, problem solved :)
[Nexus 4 Original Android Development] zakkyzombie:
Thanks man! Any bugs, or issues?

I just want to be sure its DD ready. About to go on a trip, and I want something new to play with.

NEXUS⁴