yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gautam_nexus:
Perform a factory reset and then do q clean install use the gapps from OP...
[Samsung Galaxy Nexus] molesarecoming:
what gautam says, gestures typing is part of the gapps. aosp IME wont do it. the one linked on the opning page does it just fine, at least in english and german - other languages i havent tried.
[Samsung Galaxy Nexus] molesarecoming:
we wanted to do that, and will. 4.2 came right in between and we threw all our plans aside for a moment. we'll actually do something with that one that will blow your mind. it'll be a similar stretch as rom-scene-common fixed navbar-color compared to pa's per-app-color.
[Samsung Galaxy Nexus] gautam_nexus:
@moles: thanks for directing me towards twrp it's awesome and so easy to use... Makes cwm look so old
[Samsung Galaxy Nexus] molesarecoming:
you tried this? http://xdaforums.com/showthread.php?t=1942309 ;)
[Samsung Galaxy Nexus] tibey:
i would be carefull with twrp, just made a factory reset with latest version and almost all my data in /sdcard is f*cking gone (just a few useless folder left)...

edit : turns out all the files are in /data/media ! , it mounted /sdcard to /data/media/0 which was almost empty from a previous 4.2 rom..that's a relief
[Samsung Galaxy Nexus] daryelv:
4.2 Multi-user support has thrown the Recoveries situation for a loop. People NEED to be on 4.2 supported recoveries before flashing 4.2 ROMs. Make sure the version of TWRP or CWM you're using is 4.2 capable.

Is there anyway to force a verification in the updater script that this ROM (and other 4.2 ROMs) are being flashed on a) the correct device and b) a suitable recovery in installed?

-Daryel
[Samsung Galaxy Nexus] tibey:
I was using latest recovery, i guess that twrp check after the factory reset if there is a folder /data/media/0, and if so it mount it to /sdcard otherwise it mounts /data/media instead. Since i already tried a 4.2 rom and didn't wiped the 0 folder after getting files back to /data/media the result was a little bit messed up for my case..
[Samsung Galaxy Nexus] molesarecoming:
couple of banners
[Samsung Galaxy Nexus] gautam_nexus:
Gay love moles....thanks again...love your work and your taste...:D
[Samsung Galaxy Nexus] cocchiararo:
i beg to differ, i tried with one of my not so usefull packs which did not pack the google latin ime, and it had gesture typing :P

(what im saying is that the AOSP latin ime did have swype like typing)
[Samsung Galaxy Nexus] guillermo1996:
WOW! I didn't know about that! It's simply amazing :D

Thanks a lot moles, again
[Samsung Galaxy Nexus] soulaiman:
First of all thanks for the excellent ROM. It is stable (kind of).

A few points that need attention:

-sometiles the stock browser displays that it is still loading the page while the page itself is fully loaded.

-you can't set a pattern for the lockscreen because the app in the settings menu is not displayed correct

-when first installing whatever version of the ROM you will het a random reboot after some minutes

-comopared to the stock ROM some apps run slughish. Especially apps where you have to scroll a lot like livescore...
[Samsung Galaxy Nexus] molesarecoming:
1. browser - theres nothing we can do. writing a browser needs years of research and study - open a ticket in googles bug tracker

2. flip to landscape - but will be fixed soon

3. known, over the last 30 or so pages we're trying to resolve it

4. nah. the performance is 1to1 the same compared to stock - its the same thing, both are based on the same code.

keep in mind, performance is complex. things like the state of ram, running background apps, compromised memory manager because of too many installs or deliberate fc's, etc. overall i measured no differences. when you see the performance is going down make a reboot - this does the same as on your desktop computer, memory leaks get cleared, etc. in that aspect android is not yet over the hill, especially not 4.2 which has known official leaks and bugs.
[Samsung Galaxy Nexus] Painkiller006:
Idk what's been going on but the rom has never given me any problems till now :(

1) Data and APN still won't show up unless i keep wiping cache and delvik. I was on 2.99 +1 when i flashed 2.99 beta3. I have reflashed the ROM, Gapps and still have the little issue.

2) While having the headphone jack connected any music player crashes when i try to change the volume using the volume keys or in the volume settings. Even the launcher UI crashes while changing the volume without any music player being used.

Maybe i have a bad download or something, so gonna redownload everything from the OP. Gave me no bootloops when i restore apps so that was good :)
[Samsung Galaxy Nexus] MaLiXs:
restoring PA setting is ok now ?
[Samsung Galaxy Nexus] musashihatred:
Have you flashed any mods?

@k: yap. Its pretty good. I mean. I was also worying about the bugs but i just jumped into the boat of 4.2. Best. Ever. Did not messed anything. As for the thin line in status bar. I got it every time i set an odd number value.

I just restored 60 apps with rom tool box and doesnt boot loops.
[Samsung Galaxy Nexus] Painkiller006:
Nope, no mods. The only thing i flash were the ROM, Gapps, and Trinity Stable (TNP1420-512-JB-4.1.2-STABLE67)
[Samsung Galaxy Nexus] drnbrk:
How to install CM10 circle battery mod or png files?
[Samsung Galaxy Nexus] neoofoox:
I had to restart my phone because I flashed a kernel and saw that the boot animation shows 2.x.

Then I asked myself if there will be a new boot animation with 3.x? would love to see a new one. Despite the current one looks awesome too.
[Samsung Galaxy Nexus] :
I'm having the same problem. Every time I reboot my phone, I lose data connection. Only wiping cache and dalvik bring it back.

It's pretty frustrating if you have to reboot your phone a lot.
[Samsung Galaxy Nexus] Painkiller006:
Yeah it gets a bit frustrating but nothing a little reboot can't fix, it's been happening since 2.99 preview 1
[Samsung Galaxy Nexus] molesarecoming:
you might wanna do a clean factory reset, wipe dalvik & cache just to be sure. take the gapps from the op. im rebooting a hundred times a day because im working on it - not once have i lost data connection. somethings broken in your install. also i wouldnt flash 4.2.1 kernels over 4.2 --- dunno if it makes a difference but just to be safe.
[Samsung Galaxy Nexus] molesarecoming:
yeah we'll think of something. :cyclops:
[Samsung Galaxy Nexus] pixel2tech:
MOD] [GNEX] BEATS+XLOUDER! 4.1.2/4.2 [20/11/12] JB Louder Audio Improvement Patch would this mod work on this ROM using Franco s kernal
[Samsung Galaxy Nexus] MaLiXs:
i use dspmanger(from CM) mod made by myself
[Samsung Galaxy Nexus] pixel2tech:
Were can I get zip
[Samsung Galaxy Nexus] Joplisan:
I noticed that I lost data connection when turned PA colors on. When turned off, everything worked fine. All that happened while on Franco kernel, now with stock, everything works fine. PA colors activated, connection working like a charm. I don't know how much sense does it make, but it works now, and that is what matters. :)
[Samsung Galaxy Nexus] cocchiararo:
you crave for 4.2.1 to drop SO much that you always type that instead of 4.1.2 xD

ps: i deleted all the gapps that i had linked before, they were all a mess xD (each time i tried to improve the package you took as base, i broke something new :P. Im still trying tho, but wont post anything until it is indeed better :P )
[Samsung Galaxy Nexus] saw81:
First, thanks to the work performed!!but i have a problem .. everything works fine but when I restart the phone have bootloop. I need to make a wipe dalvik cache for boot.

I tried to change kernel but the problem remains.. I only installed applications with titanium backup,without data..thx
[Samsung Galaxy Nexus] gerberman:
Anyone else getting "android is upgrading" every time their phone reboots? (not only after flashing something)

I'm using paranoid 2.54

Sent from my Paranoid Powered Galaxy Nexus
[Samsung Galaxy Nexus] MaLiXs:
https://www.dropbox.com/s/0twwsf4ymdgmhgh/dsp_manager.zip
[Samsung Galaxy Nexus] pixel2tech:
Thanks a lot
[Samsung Galaxy Nexus] MaLiXs:
then press the thank button on my post ;)
[Samsung Galaxy Nexus] DoesntPostAThing:
No. Every power on. I don't get any random reboots, or lag.
[Samsung Galaxy Nexus] Painkiller006:
no factory reset, just flashed the rom again, gapps, wipe dalvik & cache and it runs smooth. Left the kernel alone and reboot the phone 3 times, data is holding up. Must of been something with the kernel o.O

Edit: I'm guessing it was my fault for using a 4.1.2 Kernel on a 4.2 Rom...never crossed my mind not to mix those two, silly me lol :(
[Samsung Galaxy Nexus] DoesntPostAThing:
I'm starting to think that it's not a specific app, but either just pure luck or the number of apps. It seems that if I restore a few apps, yes, using TB or RTP, I still get no bootloop. Restore some more, and bootloop.
[Samsung Galaxy Nexus] bostonbassman78:
Well I just got the bootloop issue mine was caused by me letting my phone get to 2% battery then it just kept trying to reboot itself all is good now I wiped cache and dalvik cache rebooted and its

Sent from my Paranoid N7
[Samsung Galaxy Nexus] nikulogical:
just a thought, doesn't PAOSP look better than AOSPA and make more sense due to the shared meaning for A.
[Samsung Galaxy Nexus] DoesntPostAThing:
Paranoid Android Open Source Project. Makes more sense to me.

Also, I'm beginning to think the loss of data connection/APNs and the bootlooping are linked. When I get a super-long boot (I didn't delete the cache file), I usually end up with no data connection and no APNs. The carrier info also changes from just ROGERS to CAN Rogers Wireless Inc. Usually it only shows CAN Rogers Wireless Inc. during the first few seconds after booting up.
[Samsung Galaxy Nexus] indoline:
+1
[Samsung Galaxy Nexus] someonesim:
Not sure how this will help input the SOD issue, but upgrade from 2.99.1 to 2.99.3, install rom install gapps install trinity a4, wipe cache wipe dal-vik cache, reboot, restore papref, reboot, then done. After long night sleep, screen failed to wake. Last time i'm having SOD was the morning after fresh 2.99.1 install. I have TiBu but didnt restore anything since no need of it.
[Samsung Galaxy Nexus] bostonbassman78:
Lot of ppl are haviving issues or had issues with a4 including me I'm just sticking to stock kernel for now

Sent from my Paranoid N7
[Samsung Galaxy Nexus] mariachi202:
Did you wipe data/factory reset before you flashed the rom?

Moles, any way to disable navbar without removing the status bar?

Fullscreen app toggle doesn't seem to be working with the new PA framework, although it seems to be working with other AOSP based roms.
[Samsung Galaxy Nexus] Painkiller006:
You might want to change the Kernel seeing as how the one you are currently using is for 4.1.2 and this version of PA is a 4.2 ROM. I just noticed this myself thanks to Moles so i changed the Kernel to Trinity Alpha4 and it works fine, no data or APN lost.
[Samsung Galaxy Nexus] alahkel:
+1
[Samsung Galaxy Nexus] molesarecoming:
i know but paosp sounds weird if you speak it as a word : P

doesnt matter aospa = aosp + paranoidandriod, aospa is a variety, not the roms name, which is paranoidandroid anyway
[Samsung Galaxy Nexus] Nephilim:
You can call it AOSPAQ8I0#*0JLKIO 3+ for all I care, I just want to flash it!!!!!!
[Samsung Galaxy Nexus] bostonbassman78:
Lol

Sent from my Paranoid N7
[Samsung Galaxy Nexus] HwyXingFrog:
Indeed. I went from 2.54 to 2.99.1 to 2.99.3 and I love it.
[Samsung Galaxy Nexus] bostonbassman78:
I agree 100% best ROM out there best team just the best at it all lol

Sent from my Paranoid N7
[Samsung Galaxy Nexus] SplitCold:
Couldn't get a data connection with this rom.
[Samsung Galaxy Nexus] DoesntPostAThing:
So I took a logcat of the "bootloop". I put my phone into recovery mode, and when the boot animation started, I started the logcat. When the boot animation looped, the logcat stopped. Here's the logcat. The last line read:

[ 11-26 18:27:01.265 389: 572 I/ActivityManager ]

Process com.anddoes.launcher (pid 649) has died.

com.anddoes.launcher should be Apex Launcher, right? So maybe the bootloop has something to do with that? I usually restore my Apex desktop with my other app settings, so I don't really know which one is causing the loops... Other people getting bootloops, are you using Apex too? And people not getting bootloops, are you not using Apex?

On a side note, I applied the (awesome) holo theme in TWRP and now I can't set a custom backup name? Strange? I'm on TWRP 2.3.2.1, if that makes any difference.
[Samsung Galaxy Nexus] nikulogical:
When I was getting boot loops, apex was one of the things I restored.

I redownloaded apex from the apo store and not getting boot loops.

However in both cases, apex is NOT my default launcher.
[Samsung Galaxy Nexus] DoesntPostAThing:
Yes, I noticed that I started getting bootloops after I installed Apex. I always restore Apex though, to restore my theme. The one time I did download it from play store, and manually themed it, I still got bootloops :(

Also, I found another few lines in the logcat that might have caused the data connection issue, if you had waited out the bootloop.

[ 11-26 18:26:51.070 389: 410 E/MobileDataStateTracker ]

default: Ignoring feature request because could not acquire PhoneService

[ 11-26 18:26:51.070 389: 410 E/MobileDataStateTracker ]

default: Could not enable APN type "default"

EDIT: I removed Apex, still bootlooped :/
[Samsung Galaxy Nexus] curious_yellow_eyes:
Could be, I've had no data issues whatsoever though.

Also, restoring Apex certainly didn't cause my bootloop because I've never had apex.
[Samsung Galaxy Nexus] DoesntPostAThing:
Yea, I tried removing Apex, and still got bootloop. My current workaround with the wiping dalvik cache file script at boot is working pretty well, though. I also flashed Franco Kernel r328 no problem (I was getting bootloops before flash). In general, I'm quite happy with the ROM.
[Samsung Galaxy Nexus] m.is.for.michael:
To those having data connectivity issues, I raised this almost a week ago on 2.99.1: http://xdaforums.com/showthread.php?p=34467892#post34467892

As I see it, my problem was that the APNs weren't being registered properly; I couldn't create new ones either (at least, they didn't show in the list when I pressed save). When I did a battery pull, the old APN (and the new ones) reappeared, and I had data connectivity.

The bit of logcat which I thought was relevant was this:

I/SystemServer( 390): Connectivity Service
D/ConnectivityService( 390): ConnectivityService starting up
E/ConnectivityService( 390): Ignoring protectedNetwork 10
E/ConnectivityService( 390): Ignoring protectedNetwork 11
E/ConnectivityService( 390): Ignoring protectedNetwork 12
I/ActivityManager( 390): Config changed: {1.0 ?mcc?mnc en_US ldltr sw360dp w360dp h567dp 320dpi nrml port ?uimode ?night finger -keyb/v/h -nav/h s.3}
W/ApplicationContext( 390): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1407 android.bluetooth.BluetoothPan.:141 android.bluetooth.BluetoothAdapter.getProfileProxy:1164
E/MobileDataStateTracker( 390): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 390): default: Could not enable APN type "default"

I'm not sure what a Protected Network is, but if something is blocking access to the APNs then it follows the phone won't be able to use them to create a data connection.
[Samsung Galaxy Nexus] DoesntPostAThing:
I also noticed the APN problem while I was poking around mobile network settings trying to fix my data connection. Could it be the data problem that is causing the bootloops? And in the end the phone gives up, boots, but with no data? No clue, just guessing here.
[Samsung Galaxy Nexus] decalex:
I had the same issue - could have been placebo, but i flashed new radio and it worked after.

Sent from my Paranoid GNex
[Samsung Galaxy Nexus] DoesntPostAThing:
Is the new radio XXLH1? If so, I already have the new radio.

---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------

Was it after a lengthy bootloopy boot? If so, run this script every boot:

busybox rm /data/dalvik-cache/system@framework@android.test.runner.jar@classes.dex
[Samsung Galaxy Nexus] :
Looks like I'm not the only one with the data connection loss issue. This at least proves that the issue is not hardware related.
[Samsung Galaxy Nexus] musashihatred:
I also had the lost apn but not the bootloops. -_-
[Samsung Galaxy Nexus] decalex:
Yea, that's the newest. I flashed uglh, but only out if necessity. (Was driving, lol). Otherwise, would have done a logcat to see what the issue actually was. ..unhelpful post. ;)

Sent from my Paranoid GNex
[Samsung Galaxy Nexus] lurchi17:
Don´t know if somebody already posted it, but maybe you didn´t see it: http://xdaforums.com/showthread.php?t=2012756 ;) (currents should be the reason for the lags)
[Samsung Galaxy Nexus] DoesntPostAThing:
Thanks, this would've been really useful when I was on stock 4.2. PA is super smooth for me, but some people have really bad lag so this might help.
[Samsung Galaxy Nexus] pmbabu:
I went one step further and just disabled the whole Currents app. It wasn't causing lag for me (on PA2.99+3 & Franco's r318) but surely was causing huge battery drain.
[Samsung Galaxy Nexus] decalex:
Awesome- -thank you for that.
[Samsung Galaxy Nexus] dedraks:
Latest PA + Zen V8 working like a charm here.

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] anoraknophobia:
Really ? I tried AK, Zen and Franco and all kernels gave me massive problems. Franco didn't even boot up. Ended in a bootloop. :/
[Samsung Galaxy Nexus] vaizard:
here also no prob with Zen V8 but i had problems with trinity..

Zen is working like a charm..
[Samsung Galaxy Nexus] pmbabu:
Trinity a4 gave me SOD. I am now on r318 of Franco (PA2.99+3 of course!) and there have been absolutely no problems whatsover. All settings on Franco kernel are default except for colors. I use Trickster Mod to set the colors to morfic. I am staying away from r325-r328 versions of Franco's as many users have reported one problem or other and r318 works great.
[Samsung Galaxy Nexus] molesarecoming:
i might have found the issue thats bogging down pa currently. it sounds dumb, but when i take out the media folder, which contains the bootanimation and exchange it with aosp stock media - it boots up flawlessly------ :confused:

it could be that ours is too big for 4.2, maybe it doesnt have enough memory left to load packages or whatever the reason. but beta 4 will FINALLY be clean. im kinda angry that this stupid thing has cost us a week. i dont feel like i have done anything wrong by supplying a bootanimation that has worked for half a year.
[Samsung Galaxy Nexus] simacai:
franco r328 and pa combo works perfect here...

clear fku app data and disable PGM before boot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
great looking forward to next build..will defiantly try 4.2 pa this time :good:

---------- Post added at 04:43 PM ---------- Previous post was at 04:43 PM ----------

been using r328 for 2 days works without any issues.. but trinity a4 gave me SOD as well
[Samsung Galaxy Nexus] cocchiararo:
No data restore or gapps fault? Or this is related to the first long boot?

Ps: Android 4.2.1 suposedly dropping right now for nexus 10

--

Tapatalk2
[Samsung Galaxy Nexus] Khizar:
i flashed without clearing data and it worked great.. had problem the first time and went to r327 but reflashing fixed whatever issue i had

---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------

yeah but its a 1mb file.. not big fixes expected
[Samsung Galaxy Nexus] :
That's good to hear! Any chance that could also fix the data connection issue? The boot animation being too large doesn't leave enough memory to load the radio-related files, maybe? I'm really a noob when it comes to this kind of stuff.. :confused:
[Samsung Galaxy Nexus] molesarecoming:
i think its all related. the first boot up is what really bugs me - people destroying things with tibu, that will happen in future aswell but probably not as bad as over the last 50 pages. but yeah, im scratching my head right now, its the dumbest thing that's ever happened to pa.
[Samsung Galaxy Nexus] rshankar:
Hey, using 2.99B3 and I haven't changed the kernel. But anyone know why the Google Play Services takes up so much battery? Thanks
[Samsung Galaxy Nexus] molesarecoming:
if this thing is fixed, and as i said, its the fricking bootanimation-who would've thought, then we're back to clean aosp. whatever issues arise later are either local or caused by aosp itself. i know data works and i know it survives any reboot so im pretty much assured there'll be not much to look into. i suggest when the new preview is out, hopefully today, you'll try a clean fresh start - thats what i would do.
[Samsung Galaxy Nexus] someonesim:
Saw news that 4.2.1 OTA to Nexus 4 and Nexus 10, see how many bugs it fixed, or how many more bugs added . . . . :p
[Samsung Galaxy Nexus] molesarecoming:
best news ever! i take this %&$& too personal, when theres bugs. :p
[Samsung Galaxy Nexus] Khizar:
lol so the only thing that 4.2.1 fixes is the december bug...everything else is same
[Samsung Galaxy Nexus] m.is.for.michael:
Not to rain on your parade, but are you fricking serious?

The PA bootanimation is 9MB or thereabouts. I have made a few animations (<shameless plug>amongst the excellent ones here</shameless plug>), and the largest one was just over 90MB and booted perfectly in PA 1.something with absolutely no problems (well, it lagged horribly during the animation, but that's kinda to be expected with such a large file; Android ran fine though).

I'm just pushed it to my phone (running 2.99.3) and rebooted with no dramas at all.

(needless to say, I've subsequently removed it... ahem... anyone got a copy of the bootanimation from paranoid?... oh, nvm. it's in the rom.)

In short, I highly doubt it's the animation (which I REALLY like, by the way).

Have you checked the contents of ./audio between what's in PA and AOSP? Even that's a long shot, and you're more likely to have hit on a coincidence.
[Samsung Galaxy Nexus] :
Just to be sure, I'll first dirty-flash the new beta over beta 3 and flash 4.2 radio on top of it. If I still get the issue, THEN I'll do a clean flash.

I don't want to do a full wipe unless very necessary, because I'll have to download all the stuff again and that eats up all the megabytes in my data plan.

Maybe I'll go for Titanium Backup... But reading all the complaints about it really doesn't encourage me to use it at all.
[Samsung Galaxy Nexus] haxor:
No its not like that.

http://www.talkandroid.com/142177-nexus-10-now-receiving-android-4-2-1-update-fixes-december-bug/
[Samsung Galaxy Nexus] molesarecoming:
as i wrote, exchange the media folder and thats it. clean bootup. i have no idea how and why, but thats as it is.
[Samsung Galaxy Nexus] cocchiararo:
But the issue is on first boot, you should add your animation to he pa zip and do a clean install to test it xD

--

Tapatalk2
[Samsung Galaxy Nexus] Khizar:
actually it is the only fixes were the december and bluetooth bugs which were already fixed on most custom roms, so i dont even see the point of releasing 4.2.1
[Samsung Galaxy Nexus] molesarecoming:
i dont know if its the bootani - its just a wild guess but the media folder contains only three things, sounds, some vids, bootani. i can switch bewteen ****ed up boot and clean boot in an instant now, so its definitively that.
[Samsung Galaxy Nexus] molesarecoming:
wait till you see the commit log on googles git. i bet it'll have hundreds of changes made. aosp is closed source - they release when they have a milestone. when they do the full changelog is in the commitlog, blogs usually have no idea.
[Samsung Galaxy Nexus] Khizar:
hmm.. i wasnt really saying that cuz of the blogs, when i saw the file size is only 1mb i assumed there isnt much change