yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] iB4STiD:
lol, phone was freshly flashed with google 4.2.2 image so no apps, odd if cm10 doesnt trigger it seems like a bug.. people check yours wanna see if im lucky one :)
[Nexus 4 Q&A, Help & Troubleshooting] iB4STiD:
ya, its a 4.2.2 bug, decided to downgrade to my 4.2.1 rom and no problems
[Android Q&A, Help & Troubleshooting] jatinrungta:
How do I extract boot.img from Xperia U

I already got many images but while unpacking they all say android magic header not found stopping using many tools

I used android kitchen and all

one more thing

i made rom using android kitchen and then when i boot

wifi,bluetooth and phone aint working

Help Me

:crying:
[Android Q&A, Help & Troubleshooting] elektrik2001:
Have you tried this link? I find it helpful for the single core A8 Cortex (Polaroid) tablets when I have to access the boot.img. Look about halfway down for the "Boot partition" section.

Hope this helps.

https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
[Android Q&A, Help & Troubleshooting] xSkArx:
Use championswimmer tool http://xdaforums.com/showthread.php?p=26229528
[Android Q&A, Help & Troubleshooting] XDA_Bruno:
rename it to kernel.elf and it can be extract either via flashtool or kitchen (kernel tools etc)
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Hi so my friend owns a P1000

I followed this guide to try and install CWM

http://theunlockr.com/2012/05/07/ho...-on-the-galaxy-tab-p1000-running-gingerbread/

Well after going to download mode and connecting to Pc via the UsB cable..

Odin became like this

I became worried after all the box becamr yellow.. Well that picture is after i unplugged tab again.. First box was yellow having "0com30"

What should i do? Should i press start?? If not please provide me anothsr tutorial... And odin did brick her tab once before so am not taking steps with it..

Heres her about phone

Please tell me what should i do

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] yash.pranjale86:
So silly,

DON'T TRY ODIN

try android download tool (ADT)

Hope u will get it flashed

Or just flash it using recovery manager.
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Please do the "google" many devices get bricked this way by using ADT and RomManager. I just want a safe way. Flashed many roms and recoverys in odin in my Galaxy Mini never saw sonething like this where all the Boxes turn yellow.. This creeped me up..

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] jd1639:
The yellow boxes are a good thing. Find cwm in PDA and flash it. That will put the custom recovery on your phone.

Edit: the other responses you got are full of s...t
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
There should be one yellow box the first one? Why are all the boxes yellow.. I have the pda provided by chainfire to root 2.3.3.

I mean onl the first box should go yellow right?

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] jd1639:
I concur. Op, what else do you have connected to USB? Unplug them
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Nothing really. Only the phone with USB cable.. Kies ajd drivers all are installed

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] jd1639:
Have you tried to flash? I would. It'll either work or it won't, but it won't brick your tab.
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
I am really afraid man.. First she bricked her tab with odin once without knowing anything.. And now if i brick her tab again she gonna go nuts lol..

Anyways you sure? We shouldnt play with bootloaders..

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] jd1639:
OK, you're in a bad spot, lol. I'd get odin version 1.85, never had luck with 3. And then see if you still get all the yellow boxes. Then make sure cwm is for your specific device, double check that. Then flash, I'm sure that will work.
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Thanks a lot mate.. Can you provide me odin and cwm link?

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] jd1639:
Check the stickies in the development section for your device on xda for cwm or twrp. Google for odin.

God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
DDJPA is an indian Stock rom ...read somewhere the bootloaders are locked..i have NO plans of unlocking them cuz there is a high chance of scrwwing things up..read Chainfires thread he had no CF-root kernel for DDJPa..need help guys

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Just use overcome method. The gb stock safe v5 packaged by them is stock jq1 with bootloader.

It will replace your locked bootloader.

Then overcome kernel will provide you a cwm.
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Please i dont really wanna brick it..can you provide a tutorial or a link

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
It is all there in my signature. The guide is a pdf.

Read from page 7 of pdf.
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
any tutorial? sorry i am kinda noob with samsung devices

-Rik[Rittik]
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Did you even read the PDF?
[Galaxy Tab Q&A, Help & Troubleshooting] Rittik:
Couldnt find it..it took me to the CM10 thread . Nvm found jt

-Rik[Rittik]
[Samsung Galaxy Nexus] ak:
Im testing right now and porting SCH_NET from linux stable branch ... :D

Thanks a lot for your great work.
[Samsung Galaxy Nexus] lioux:
SCH code from Linux 3.3 onward is based on Byte Queue Limits (BQL) which breaks compatibility with previous kernel code. It tracks bytes queue lenght instead of packets. It's both a saner and a more precise measure since packet size varies with MTU amongst other things. So 1 packet does not mean the same for every installation.

You might be able to import the *sch* files and use them with the compat.ko kernel module.
[Samsung Galaxy Nexus] ak:
I have implemented it into my kernel ... how can i verify performance? :fingers-crossed:
[Samsung Galaxy Nexus] lioux:
Dave Täht from BufferBloat project has given the following reply. I'll try to elaborate a script based on his suggestions.
[Samsung Galaxy Nexus] lioux:
You should be able following my guide below. A couple things though:

1) fq_codel is tuned to Gig networking per default.

1.1) The following patch should alleviate to our sub 10Mbit network (radio) without much effect on our WIFI traffic

diff --git a/net/sched/sch_fq_codel.c b/net/sched/sch_fq_codel.c
index a7b3754..c765e6c 100644
--- a/net/sched/sch_fq_codel.c
+++ b/net/sched/sch_fq_codel.c
@@ -387,7 +387,7 @@ static int fq_codel_init(struct Qdisc *sch, struct nlattr *opt)
struct fq_codel_sched_data *q = qdisc_priv(sch);
int i;

- sch->limit = 10*1024;
+ sch->limit = 600;
q->flows_cnt = 1024;
q->quantum = psched_mtu(qdisc_dev(sch));
q->perturbation = net_random();

2) From my extensive testing, we should be safe to

# echo 0 > /sys/class/net/p2p0/tx_queue_len

# echo 0 > /sys/class/net/rmnet0/tx_queue_len

# echo 0 > /sys/class/net/wlan0/tx_queue_len

3) In case, you've codel the default instead of pfifo_fast... just make sure you've chosen fq_codel. That's the apropriate one. If not, we still need a startup script that would do

# tc qdisc add dev p2p0 root fq_codel

# tc qdisc add dev rmnet0 root fq_codel

# tc qdisc add dev wlan0 root fq_codel

# echo 0 > /sys/class/net/p2p0/tx_queue_len

# echo 0 > /sys/class/net/rmnet0/tx_queue_len

# echo 0 > /sys/class/net/wlan0/tx_queue_len

I've been running this setup for the past 24 hours. Everything seems to be fine. :)
[Samsung Galaxy Nexus] ak:
Thanks lisan for your hard work :thumbup:
[Samsung Galaxy Nexus] lioux:
For anyone wanting to test either codel or fq_codel, use the AK Cylon kernel:

http://xdaforums.com/showthread.php?p=38967264#post38967264

They're both implemented and I've sent the developer TCP Small Queues patch which should be enabled after cylon version 733

http://git.kernel.org/cgit/linux/ke.../?id=46d3ceabd8d98ed0ad10f20c595ca784e34786c5

AK is doing its part on being the lowest network latency kernel out there. :) Power to AK kernel.
[Samsung Galaxy Nexus] jawz101:
I'm trying your tests with @mrg666 kernel for the Nexus 4 since he has codel in his kernel but my results were not conclusive.

+----------------------+--------------------+--------------------------+-----------------------------+------------------------------+
| CODEL | FING avg ping (ms) | NETPING avg/std dev (ms) | NW LATENCY CKR DNS avg (ms) | NW LATENCY CKR HTTP avg (ms) |
+----------------------+--------------------+--------------------------+-----------------------------+------------------------------+
| DISABLED | 328 | 304/50.1 | 243 | 238 |
| DISABLED + UPLOADING | 333 | 354/98.8 | 257 | 268 |
| ENABLED | 293 | 329/52.4 | 253 | 253 |
| ENABLED + UPLOADING | 328 | 340/94.8 | 310 | 296 |
+----------------------+--------------------+--------------------------+-----------------------------+------------------------------+

... though I don't know if this means anything to you but the results of these commands didn't look the same as yours:

root@mako:/ # tc qdisc add dev wlan0 root fq_codel
tc qdisc add dev wlan0 root fq_codel
Android does not support qdisc 'fq_codel'
RTNETLINK answers: No such file or directory
2|root@mako:/ # tc -s qdisc
tc -s qdisc
Android does not support qdisc 'prio'
qdisc pfifo_fast 0: dev rmnet_usb0 root refcnt 2 [cannot parse qdisc parameters]
Sent 4224 bytes 36 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
Android does not support qdisc 'mq'
qdisc mq 0: dev wlan0 root
Sent 32731522 bytes 27551 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
Android does not support qdisc 'mq'
qdisc mq 0: dev p2p0 root
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0

---------- Post added at 08:30 PM ---------- Previous post was at 08:00 PM ----------

... maybe because he has codel enabled- not fq_codel... grr
[Samsung Galaxy Nexus] dtaht:
correctly testing fq_codel

There are multiple things wrong here.

-1) fq_codel is not visibly attached to anything. The errors got earlier indicate that:

0) it doesn't look like your iproute2 is updated to support fq_codel statistics or parameter setting. Get iproute 3.6 or later installed.

1) If your bottleneck link is elsewhere (say at the DSL modem), adding fq_codel does no good on the handset. Put a SQM qos system there.

Or test against a local server to stress out your wifi, if that' what you are testing. if you are testing 3g, you can't do much about

2) The "mq" qdisc on wifi would need fq_codel queues attached to work properly, not just one, but usually 4.

a script like this does that...

https://github.com/dtaht/deBloat/blob/master/src/debloat.sh

alternatively you can just make fq_codel the default as openwrt did so it automagically attaches to the mq

<pre>

# Wifi is special in that how the queues work is pre-defined

# to be voice, video, best effort and background

QDISC=fq_codel

FQ_OPTS="quantum 300 limit 1000"

IFACE=wlan0

wifi() {

tc qdisc add dev $IFACE handle 1 root mq

tc qdisc add dev $IFACE parent 1:1 $QDISC $FQ_OPTS noecn

tc qdisc add dev $IFACE parent 1:2 $QDISC $FQ_OPTS

tc qdisc add dev $IFACE parent 1:3 $QDISC $FQ_OPTS

tc qdisc add dev $IFACE parent 1:4 $QDISC $FQ_OPTS noecn

}

wifi

</pre>

3) in most cases the underlying driver buffering and tcp stack are horribly overbuffered in the first place,

so applying fq_codel doesn't work as well as it could were these tighter. you will generally get better

latency regardless but not hugely so unless those problems are resolved also.

inf) We have a huge list of things that people have done incorrectly detailed here:

https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel
[Samsung Galaxy Nexus] jawz101:
The man himself!

Pretend I did that wrong and it really has codel enabled as opposed to fq_codel... are the same comments applicable? I'm just learning and experimenting with his kernel. Thanks!

While were at it someone on your listserv mentioned another bottleneck with mobile devices being that the manufacturers use BQL a lot and there isn't anything we can do to disable it. And WiFi & cellular radios go through the USB bus on phones which are another issue. I'm in uncharted territory so I probably got some terms mixed up.

Edit: this post

https://lists.bufferbloat.net/pipermail/bloat/2013-February/001371.html

...And I guess that was you two talking there
[Samsung Galaxy Nexus] dtaht:
tryin

0) I don't have a whole lot of time to build android. I'll gladly test a version at some point...

There isn't a lot of point to codel by itself, it's with fq_codel that shines. We continue to use codel

as the algorithm and fiddle with it in conjunction with other fq methods...

yes, it's uncharted territory.

I appreciate your willingness to explore, and hope that eventually you'll get there. Personally I've had more hope that the device manufacturers would "get it" and start actively managing their queues better on newer devices.

1) The first error shows fq_codel was not added successfully to the qdisc for the device, therefore you aren't benchmarking it.

perhaps it needs to be

modprobe sch_fq_codel

first? see if the module is in /lib/modules (find /lib/modules -name sch_fq_codel.ko)

root@mako:/ # tc qdisc add dev wlan0 root fq_codel

tc qdisc add dev wlan0 root fq_codel

Android does not support qdisc 'fq_codel'

RTNETLINK answers: No such file or directory

2|root@mako:/ # tc -s qdisc

The following errors show that iproute2 is out of date, at the very least, incompatible at worst.

usb network devices are generally overbuffered. While BQL would help here, nobody's got it hooked up yet.
[AT&T Samsung Galaxy Note I717] OPGT:
I

Sources: https://github.com/jellybam & https://github.com/igio90 & github.com/cyanogenmod :Sources​

First Off, Credit goes to iGio90. This is no means my rom and i'm aloud to post this ROM according to this

and give credit where due. On the OFFICAL FaceBook page.

Want to Donate?

​

FEATURES​

BUGS

Downloads & Installation

download JellyBam Mod Edit

Wipe data

wipe cache & dalvik cache

Flash ROM

Reboot

Enjoy

​

FAQ

***ChangeLog 27/02/2013​

**again all credit goes to iGio90 who developed the ROM**

Credits

Chris41g

AOKP team

Cyanogenmod Team

Paranoid Android Team

Carbon Team

PAC-Man Team

Paintball2345 For helping out on this thread​
[AT&T Samsung Galaxy Note I717] JEZZEJAMEZ:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

The beta was smooth as ice, this has to be he cats meow. That for the hard work

BlA¢K ★ X

$†@¢KH○u$€ ®€D
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Very nice.....thanks.
[AT&T Samsung Galaxy Note I717] OPGT:
Seems to still be uploading.. wait for it people :)

EDIT- UPLOADED on Goo.
[AT&T Samsung Galaxy Note I717] king71st:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I already downloaded from goo

Sent from my SAMSUNG-SGH-I717 using Xparent SkyBlue Tapatalk 2
[AT&T Samsung Galaxy Note I717] unibomber:
I get a nasty flicker with this release
[AT&T Samsung Galaxy Note I717] Donjuanal:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Same here. Specifically with the keyboard open. Forcing 4x aa seems to help a little. Back to cm10.1 for now.
[AT&T Samsung Galaxy Note I717] OPGT:
have you guys tried flashing another kernel??
[AT&T Samsung Galaxy Note I717] king71st:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I've tried aces and flapps kernel won't boot get black screen

Sent from my SAMSUNG-SGH-I717 using Xparent Pink Tapatalk 2
[AT&T Samsung Galaxy Note I717] people211:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Does disabling hw overlays stop the flicker?
[AT&T Samsung Galaxy Note I717] JEZZEJAMEZ:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

No, I've also put all animations to .5 still flicker city

SmOoThEst Be@ñ
[AT&T Samsung Galaxy Note I717] unibomber:
Disabling he overlay doesn't work. I got the latest aces kernel to boot but it doesnt help.
[AT&T Samsung Galaxy Note I717] Donjuanal:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I havent. But this is the exact same issue with the cm10.1 nightly experimental build. From the 22nd
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

According to igio, this build only works with stock kernel.
[AT&T Samsung Galaxy Note I717] kimtyson:
Disabling HW Overlay does nothing. I keep getting System UI crashes. It's kind of unusable right now. Maybe released prematurely.
[AT&T Samsung Galaxy Note I717] MoJoe277:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Downloading now. Can't wait!

Has anyone tried any other kernels on this yet (4Aces or FJ's)?
[AT&T Samsung Galaxy Note I717] Scruffdog1978:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

This thread is not even 2 pages old and this has been answered.....Read!
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

This doesn't look very promising.. All the issues should I flash?
[AT&T Samsung Galaxy Note I717] unibomber:
Not yet
[AT&T Samsung Galaxy Note I717] Scruffdog1978:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

If you can deal with the flicker go ahead
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Alright i checked fast charge in perf control......now i don't know good settings for undervolting .....anyone got some expierence ... I under clock my CPU i rarely over clock ....rather have battery
[AT&T Samsung Galaxy Note I717] _INSPIREed:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Teufel By nadda do you mean it just doesn't show up ?
[AT&T Samsung Galaxy Note I717] Teufel Hunden:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Yes

Biggest dog on the block, NOTE!! 4.2 JB!
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Which tablet option are you using?
[AT&T Samsung Galaxy Note I717] _INSPIREed:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Ahh i just caught on to something you said before. You were in tablet mode . and it seems you are right . i can't get it functioning in tablet mode. But on stock it works fine.
[AT&T Samsung Galaxy Note I717] Teufel Hunden:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

The top one with 195 or whatever dpi

Biggest dog on the block, NOTE!! 4.2 JB!
[AT&T Samsung Galaxy Note I717] _INSPIREed:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Idk what the deal is with tablet mode working with pie. But if it is a must for you, might i suggest LMT launcher? Looks and behaves just like pie controls. I've been using it for a while now
[AT&T Samsung Galaxy Note I717] ZEMONTI:
Me too.

I'm sorry.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Read through past few pages ...there is a fix
[AT&T Samsung Galaxy Note I717] OPGT:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Can people not read? Lol. Please read OP.
[AT&T Samsung Galaxy Note I717] odobo:
thanks for the tips! :good::good::good:
[AT&T Samsung Galaxy Note I717] pTeronaut:
Same here, neither the power button (although long press would bring up the power menu), pre-set timeouts, or ProximityScreenOff's ScreenOff widget would turn send the phone to sleep.
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

That's exactly what I tried....
[AT&T Samsung Galaxy Note I717] king71st:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

This is what I use for fast charge https://play.google.com/store/apps/details?id=nz.org.winters.android.gnfastcharge
[AT&T Samsung Galaxy Note I717] chappatti:
After going through several options, I must say I love this ROM !!!! One could keep pushing buttons all night long !

To support IGio90 I got his Tweaker app.... That app is another button-pusher !!

One stupid question: How to turn off haptic feedback ? Man, I have looked at al options, in all menus (I think:p). Where is this option, anyone?

Thanks!
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Finally all set up!

Damn this ROM is fine!

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] CB620:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Been setting up settings for hours :D

This rom will keep you occupied.

Has anyone changed the nav buttons successfully?

Been trying to change one of my buttons to screenshot but doesn't work for me.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Cause there's 3 diff setting that do the same thing
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I changed nav buttons but said "to hell with this nav bar stuff!" Its too conflicting with my keyboard.

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] CB620:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Thanks. Ill dig deeper.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Pa preferences ...........move the nav bar slider to 0....done Nada ziltch no Nav. Bar ...... Jeezuz
[AT&T Samsung Galaxy Note I717] delock:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Is it me? I was surprised there was less settings then 4.2.1...plus it was acting strange on my phone. I went back to my backup and will redownload later.
[AT&T Samsung Galaxy Note I717] kimtyson:
Try Settings- Sounds

And (almost) no question is stupid.
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Didn't work for me just made the Navy bar dimmer. The opacity set to 0 doesn't fix it. Even if it did there's still that black bar there. :(
[AT&T Samsung Galaxy Note I717] kimtyson:
You went to System Settings- Paranoid Preferences- Interface and turned the "NAV. bar" down to 0%; then (and this is key folks) hit the check mark at top of screen? And you say nothing happens? Then you have another issue because that works.

Do you have the right ROM version for your device?

Did you wipe everything?

Did you add any other apps or restore anything before testing this?

That's all I got for ya. Redownload, wipe and install again I guess. Or admit this isn't for you.
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

If you are using any of the tablet modes....you are stuck with a nav bar.
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Exactly I was using the tablet ui that is stuck with the Nav bar. No need to be the correctional officer and make me feel bad.
[AT&T Samsung Galaxy Note I717] JEZZEJAMEZ:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Now we all get along..

BlA¢K ★ ※

$†@¢KH○u$€ ®€D