Originally Posted by unknownzero

I was in the middle of editing that post to include just that information. :P
Tried the one shipped with it, then faux, then I tried a stock kernel.

I was using v3 lately, however I have tried since v1 to get this working and have had no luck.
How long have I waited? I fell asleep for 6 hours and woke up to this X a few days ago.

I'm coming from the stock ROM IMM76K.

Flash super wipe- install rom- let it boot loop for five min...- pull battery- wipe cache partition only... reboot... should boot... had this same issue..

Sent from my Galaxy Nexus using xda app-developers app

Originally Posted by stebomurkn420

Flash super wipe- install rom- let it boot loop for five min...- pull battery- wipe cache partition only... reboot... should boot... had this same issue..

Sent from my Galaxy Nexus using xda app-developers app

I just tried this, and it didn't work. I left it on for about 30 minutes and it still showed the X. Not sure what to do now.

Originally Posted by mark manning

Anyone else have these problems???

Let us know

Sent from my Galaxy Nexus using xda premium

I had problems as well Mark... can't remember how/what app but it froze up and I had to do a couple of Batt pulls.

I finally dirty flashed the V3 ROM again and didn't add a kernel and it seems to be working fine. I have always gotten what I need out of stock anyway with the help of ExDialer, Nova Launch, Swiftkey and a few other fine tuning apps for the Droid environment.

I just now remembered what the problem was... it was BT... it wouldn't turn on and then when trying to start it it would freeze the system... well I thought my fix above (dirty flash the ROM only) would/did fix it but it just happened again... going t try and wipe the caches and check it again... I guess if nothing is better than it is time for a new (freshly and cleanly installed) ROM... maybe V1 or ???

i have a big problem... was running jb v3 with fauxs experimental kernel and my phone died.. i plugged it in tried booting up and got stuck at google screen. i tried wiping and reflashing and only a few times i actually got to the actual x boot screen and when i did it would try to boot for a second and then stop randomly and reboot itself back to the google screen, i then flashed a recovery and new kernel from before and it still wont boot, it just goes to the boot animation and then freezes and then google screen and loops like that. please help im out of ideas ive tried everything ):

Originally Posted by mark manning

If your getting lag on faux one way to resolve this is to... boot into recovery, flash the stock kernel (it will act as a reset kernel) then flash faux's over top and reboot.

Vicious uses a custom ram disk and francos kernel severely messed that up. Sometimes a lil bit of code will carry over. This should fix that for you all.


As always wipe your caches tho

Sent from my Galaxy Nexus using xda premium

Hey Mark... did you mean to say

Originally Posted by mark manning

If your getting lag on faux one way to resolve this is to... boot into recovery, flash the stock ROM (instead of kernel... as in V1?) (it will act as a reset kernel) then flash faux's over top and reboot.

If not... which version specifically are you referring to?

Thanks in advance!

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

Originally Posted by unknownzero

I just tried this, and it didn't work. I left it on for about 30 minutes and it still showed the X. Not sure what to do now.

For starters... try re-downloading the ROM file... maybe yours was not clean. It is known to happen.

Originally Posted by mark manning

Anyone missing notification toggle widgets yet???

Here is a lil secret

https://play.google.com/store/apps/d...ficationToggle

I like extended controls better

Sent from my Galaxy Tab 10.1 using Tapatalk 2

Hey Ya'll...

---

Just thought I would mention that Trinity has a new version out...

AT1689-384-JB14
md5sum: 806f2b87e16f468f7a7ff3a1517b82fd
This is the Trinity Nexus Prime Jelly Bean kernel with Max CPU and 384MHz GPU clock, includes KSM for ANY Rom (Uses rom's ramdisk). It includes adjustable vibration, tuned colors, build optimizations, leaner build..
Jul 02 2012 17:56

http://www.derkernel.com/jbtuna.php#

Originally Posted by super_dk

Use Root explorer or other such app to go into system and edit your the LCD density line of the build.prop. As you can see, I am running at 160dpi which is the dpi of the tablet ui. You can also use ROM toolbox to play with your build.prop although I didnt have much success with it.

Edit: Sorry, the attachment is not playing well with me right now.

Can you test 240dpi and let us know if that works too?

Sent from my Galaxy Tab 10.1 using Tapatalk 2

Originally Posted by veloslave

Just thought I would mention that Trinity has a new version out...

AT1689-384-JB14
md5sum: 806f2b87e16f468f7a7ff3a1517b82fd
This is the Trinity Nexus Prime Jelly Bean kernel with Max CPU and 384MHz GPU clock, includes KSM for ANY Rom (Uses rom's ramdisk). It includes adjustable vibration, tuned colors, build optimizations, leaner build..
Jul 02 2012 17:56

http://www.derkernel.com/jbtuna.php#

Is there an app to edit trinity kernel settings?

Sent from my Galaxy Tab 10.1 using Tapatalk 2

Originally Posted by veloslave

I had problems as well Mark... can't remember how/what app but it froze up and I had to do a couple of Batt pulls.

I finally dirty flashed the V3 ROM again and didn't add a kernel and it seems to be working fine. I have always gotten what I need out of stock anyway with the help of ExDialer, Nova Launch, Swiftkey and a few other fine tuning apps for the Droid environment.

I just now remembered what the problem was... it was BT... it wouldn't turn on and then when trying to start it it would freeze the system... well I thought my fix above (dirty flash the ROM only) would/did fix it but it just happened again... going t try and wipe the caches and check it again... I guess if nothing is better than it is time for a new (freshly and cleanly installed) ROM... maybe V1 or ???

The first time I had a lock up it was with BT as well. I'm good at recovering it now, but that first time scared the **** out of me. So far with the Faux kernel everything is working great including BT. I use my phone to stream through my Sync system almost exclusively when in my car so it's getting a good work out.