yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note II] Gorguts:
Now this makes sense... Thank you.
[T-Mobile Samsung Galaxy Note II] mygalaxynote2:
I have not seen any answers to these questions yet.

Are there any solutions to these problems yet?

I am planning to dirty flash this room from rooted Jelly Bean 4.1.1 for a friend, but this Jedi Master X2 seems to have a lot of issues

and the last update was 12/23/13...

Did the developers actually fix all the known problems from the last update?

Thank you guys
[T-Mobile Samsung Galaxy Note II] Ash359:
If you dirty flash from 4.1.1 to 4.3 I can almost guarantee you will have some really fugly issues.

That's just a cruel thing to do to your friend.

Sent from my Jedi MasterX Note 2

---------- Post added at 07:19 AM ---------- Previous post was at 07:13 AM ----------

The lag screen is probably the unlock effect.

I also set my minimum frequency to 300

Battery drain usually resolves itself after a few days

Stock browser sucks anyway, download a different one.

If you really want that stock browser though there is a solution in here somewhere.

But I just froze mine.

The camera issue was discussed just a couple posts above yours.

I'm not sure about that signal loss issue but one thing you need to do is either update the bootloader, flash the Wi-Fi fix, or use another kernel like Devil2 our Agni.

The dev doesn't recommend the kernel method.

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] mygalaxynote2:
Thanks alot for the reply.

oops sorry I did read the 1st post, but I forgot to mention that I will flash rooted Jelly Bean 4.1.1 to Jelly bean 4.3 via PC Odin first, and then flash this Jedi Master X2.
[T-Mobile Samsung Galaxy Note II] Ash359:
That would certainly be better than dirty flashing from 4.1 to 4.3

However the stock rooted 4.3 may still have extra files in it's system that might conflict with Jedi.

Only time I may consider dirty flashing is on a ROM upgrade. For instance going from MasterX 1 to MasterX 2.

However even then I just clean flash.

If you use a backup like titanium it's not that much hassle.

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] mygalaxynote2:
So, this is what I should do?

1) Upgrade from rooted Jelly Bean 4.1.1 to Jelly Bean 4.3 via PC Odin

2) Then wipe everything and factory reset, and take a few pictures

3) Then flash this Jedi Master X2

He doesn't have too much stuff on his phone, so wiping everything is not an issue.

Thank you very much
[T-Mobile Samsung Galaxy Note II] Ash359:
No need to wipe storage, neither internal nor external need to be wiped.

So pictures and things won't go away.

Factory reset and wipe system

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] eZdubzitmk4:
Odin will erase them
[T-Mobile Samsung Galaxy Note II] evanladoux:
ISSUE: audio pauses & resumes in both poweramp & audible audiobook playback. - as if the phone is temp possessed by something running in background.

is there a switch somewhere that I can flip for smoother running?

I've already set buffers in poweramp to max. & top priority, slight improvement, but still issue.
[T-Mobile Samsung Galaxy Note II] Note2Hunter:
Sorry if it has been answered but was there a fix for signal loss..? It's going on and off and a lot my battery percentage is melting
[T-Mobile Samsung Galaxy Note II] psycho4us4:
Look at [MENTION=4313736]vebulous[/MENTION] signature
[T-Mobile Samsung Galaxy Note II] free2saute:
If you have FC on camera go in wanam and try this before activating working for me on X2 thanks EdKeys.
[T-Mobile Samsung Galaxy Note II] Ash359:
I just did the renaming files fix.

I'll uncheck that now just to be in the safe side.

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] dragonblade1214:
So for some reason as of the past couple days and today, my battery has sudden been draining rather quickly. Has anyone else had the same problem? I don't think it's my signal or anything like that.
[T-Mobile Samsung Galaxy Note II] kushXmaster:
Check your battery info in settings. If play services is near the top, that's the culprit. And there's not much you can do to fix it besides waiting for Google to update quietly in the background.

Play Services updates with no warning or interaction on your part. It's all background. So it may have been updated and you didn't even know it.
[T-Mobile Samsung Galaxy Note II] sabresfan:
This has been my battery life with Agni Kernel today. Everything has been smooth so far.
[T-Mobile Samsung Galaxy Note II] Ianchua:
Same for me here dude! But did you OC?
[T-Mobile Samsung Galaxy Note II] benji667:
screen on time??
[T-Mobile Samsung Galaxy Note II] kushXmaster:
Just a friendly reminder, if you are gonna talk about other kernels, please do it in their respective threads. Thanks in advance guys!
[T-Mobile Samsung Galaxy Note II] sabresfan:
Yes to 1800
[T-Mobile Samsung Galaxy Note II] vebulous:
[MENTION=1361191]zuckerj[/MENTION] and I decided to do a little unofficial official Jedi MasterX FAQ on his blagmachine. You can find it here: http://zuck.com/xda/JediMasterX-FAQ.html

It's very much incomplete, but its the next-best thing. Rather than referring people to my signature, send them to this page. (the link is in my signature as well. Old habits die hard)

If you guys have any other info to add to it, PM here.
[T-Mobile Samsung Galaxy Note II] zuckerj:
Hey, if I want to add to it would you prefer me just telling you and you do it,or do you not mind another hand mucking around on the page?

I'm fine either way.
[T-Mobile Samsung Galaxy Note II] gijoe69:
Polaris office 5 force close? How do we fix it?
[T-Mobile Samsung Galaxy Note II] Ianchua:
Clear data>Remove from System app>Reboot and boom,You get a functional PO5
[T-Mobile Samsung Galaxy Note II] zuckerj:
I was going to say open documents from within Polaris, and run it at least once to do initial config. But if doing what Lanchua suggests works, much better.

Let us know if it works.

Sent from my Xoom WiFi on Kit Kat 4.4
[T-Mobile Samsung Galaxy Note II] gijoe69:
Clear data then how do you remove? I can only disable it but still closes?
[T-Mobile Samsung Galaxy Note II] eZdubzitmk4:
Use a root Explorer and delete

Sent from my Note II
[T-Mobile Samsung Galaxy Note II] zuckerj:
You can use Titanium Backup to convert to a user app. Long press item to get a context menu.

Sent from my Xoom WiFi on Kit Kat 4.4
[T-Mobile Samsung Galaxy Note II] dragonblade1214:
Thank you for the reply!

I actually used BetterBatteryStats and checked that for any weird wakelocks and I got a really hugeee culprit (or what I think it is) under the partial wakelock category.

I'm not sure if this is really the problem but I think 46m is an obscenely high number. I hope anyone might have any ideas as to what this is?

And regarding Google Play Services, I used Wakelock Terminator to prevent it from accessing wakelocks, but I'm not sure if that's the problem. Hopefully, maybe.

---

If not, I was considering just going back to 4.1.2 but I also wanted to ask about that if restoring from my Clockwork Mod backup was all I had to do. Not sure because there was a lot of updating to get to 4.3 and such.
[T-Mobile Samsung Galaxy Note II] EdKeys:
Isn't that Google Chrome to phone?
[T-Mobile Samsung Galaxy Note II] mygalaxynote2:
I think I should wait for the update since this rom still has a lot of known bugs/issues that need to be updated.

Hopefully they release the new update with more Note 3 features and less bugs anytime soon.

Thanks
[T-Mobile Samsung Galaxy Note II] zuckerj:
Argh!

Now I'm experiencing the camera issue as of this morning. I haven't made any changes to Wanam recently. As I've been fine all along with the latest Wanam this apparently is an interaction effect, I guess. What do I know?

I don't allow Play Store to update, only notify.

So the three apps I updated as of yesterday were:

1) Facebook

2) IP Cam Viewer

3) Smart Tools

Any way, guess I need to go find that FAQ I'm hosting and see what the latest solution is to this problem.

FAQ - http://zuck.com/xda/JediMasterX-FAQ.html

EDIT:

Does anyone report long term success in dealing with the camera issue using the method described in the FAQ?
[T-Mobile Samsung Galaxy Note II] kushXmaster:
That would most likely be your phone app. Meaning you made 46 minutes worth of phone calls.

Be careful blocking play services, that's what governs all of your access to all things Google. So it might screw with email app updates etc. But that one is easy to figure out if it's causing battery drain. Just look at batter under settings. If play services is above ~12% then it's probably sucking up a lot of juice.

You should be able to revert with a backup by just wiping and then flashing the backup.

---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------

Chrome to phone would be a part of the chromebrowser.apk not the phone app.
[T-Mobile Samsung Galaxy Note II] alderaan34:
I was wondering if anyone has successfully used this rom with appradio unchained?

Sorry if this has been answered tapa talks search sucks.
[T-Mobile Samsung Galaxy Note II] Ash359:
I have heard of people having success simply by unchecking keep additional csc features.

Under advanced in Wanam.

I've done the copy paste thing and the rename thing.

Mostly permanent unless I change a Wanam setting.

Sent from my Jedi MasterX Note 2

---------- Post added at 10:23 AM ---------- Previous post was at 10:21 AM ----------

Sorry, I have never heard of that. I'll have to Google it.

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] zuckerj:
OK. I think I have a simple solution for the camera. This change worked for me after reboot. We'll see how long it sticks. I imagine it will fail after the next update of Wanam (until they address this issue) but that is OK as the fix is easy (if this truly is a fix).

I did a little exploration and examination of the xml files for both the Wanam reconstruction of feature.xml and the original Samsung feature.xml.

First, a couple comments. The Wanam reconstruction is pretty sloppy. Threre is no organization of related entries, and strict adherence to a policy of consistency is not really apparent in the Wanam XML (example: capitalization is not standard at all throughout the file - and therein lies the problem).

Second, both Samsung and Wanam make use of comments in their XML which, from my reading, is not valid XML. But I digress.

I examined the Camera and Camcorder entries and compared them between both files. I only found two differences.

1) Wanam has an additional entry related to enabling the camera during a call

2) There were two instances where the Wanam file uses CAPITALIZATION and the original Samsung file does not, as relates to the camera.

This capitalization issue is rampant throughout the file, but as everything else seems to function fine we can assume that perhaps only the camera app is sensitive to this anomaly. But perhaps some other issues are related to this "feature" of Wanam's feature.xml file.

So, to the fix...

You need to go into the /system/csc/feature.xml file and make the following changes:

1) Find the entry CscFeature_Camera_ShutterSoundMenu and change the value from "TRUE" to "true" (do not include the quotes)

2) Find the entry CscFeature_Camera_CameraFlicker and change the value from "60HZ" to "60hz" (do not include the quotes)

That's it. Now reboot and see if your camera is fixed.

Again, this will probably revert every time you update Wanam until they address their XML inconsistencies.

So will will just need to go back in and fix it.

Also, in order to edit this file you will need a Root Explorer of some type. I use ES File Explorer and you just need to set your permissions for the Root Explorer-》Mount option to RW for both / and /system.

ES File Explorer also had a built in text editor you can use.

And remember to set those permissions back after you reboot.

If you have questions, just ask.

And let's hope this is a persistent solution.

FYI just tested my camera and it is still working. :)

EDIT:

I realize this may be pure coincidence, but as the change did result in a working camera, I'm going to claim it is a fix, for now. :)
[T-Mobile Samsung Galaxy Note II] free2saute:
Did you try this I did a no fc on camera yet on day 2 with everything this rom offers?
[T-Mobile Samsung Galaxy Note II] Ash359:
I suggest posting this information in the Wanam thread.

Maybe not mention the sloppiness though...

http://xdaforums.com/showthread.php?t=2383484

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] zuckerj:
Not until I know it is actually a solution.

And yes, no mention of sloppy. Good advice.
[T-Mobile Samsung Galaxy Note II] Ash359:
Well if your camera was broken, then it started working again.

Whether it's a permanent or not it may still give Wanam a clue.

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] zuckerj:
OK.

You talked me into it.

Will do it in a few.
[T-Mobile Samsung Galaxy Note II] alderaan34:
It's uses for the appradio head units, ARU allows you to mirror and control your phone from such units. I had success with 4.3 stock tmo firmware and thought this rom might work because it was based on that.

What happens is that the app uses blue tooth to get the touchscreen on the head unit to control the phone. What's happening is that the blue tooth connection fails complete the connection. That causes the touch function to not work.
[T-Mobile Samsung Galaxy Note II] tradejak66:
I rooted thinking all I wanted was stock 4.4 but I tried this and its absolutely amazing. This is my personally perfect ROM. Battery life is great, mods are great, viper music is great, the help and support is great, and it seems just as smooth if not smoother than my stock 4.4. It even gets 1000 more in quadrant than stock did. My absolute only problem is a blank spot in the notification bar but I can absolutely live with that! Thanks for my perfect ROM dudes.
[T-Mobile Samsung Galaxy Note II] evanladoux:
did anyone reply to this? I didn't catch it. request suggestions.
[T-Mobile Samsung Galaxy Note II] Ianchua:
Sounds like some sort of decoder issue.But sorry that I can't help,Not familiar with poweramp

Edit:Try finding a suitable decoder(If there is one) and see if it improves playback.
[T-Mobile Samsung Galaxy Note II] Ash359:
I haven't had any issues with power amp myself

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] zuckerj:
Hey Ash, I posted in

[APP][4.2+][2.7.2][Touchwiz] Wanam Xposed | Customize your Stock Samsung Roms

http://xdaforums.com/showthread.php?t=2383484

Is this the correct forum for the Wanam info, or should I post in a more appropriate forum?
[T-Mobile Samsung Galaxy Note II] Ash359:
Yeah that's the one

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] 3one7:
When i checkedBoth true & 60hz are lower case already. ... camera still broke

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme
[T-Mobile Samsung Galaxy Note II] kushXmaster:
Glad you're enjoying the rom.

One thing, benchmarks are more or less pointless imo. They are far to inconsistent to garner any kind of legitimacy as far as I am concerned. For instance, you can run with the same settings ten times and get ten different scores or a rom with a high score, but runs poorly lol. But they can be fun to play with at times.

The blank spot has to do with smart stay. It will be fixed in a future update, when ptmr3 has the time.
[T-Mobile Samsung Galaxy Note II] zuckerj:
Did you ALREADY copy the entries from the feature.xml.bak file to the feature.xml file as suggested in Vebulous's signature? If so, that would explain why they are already lowercase.

But, the fact that they are lowercase, and the camera still is FC'ing on you suggests that there is more to this than just a capitalization issue in the XML.

That would make sense, as I didn't think this change was going to result in any improvement, but to my surprise, for me, it resolved the FC issue.

One thing I want to ask is are you sure you haven't introduced any typos when modifying the feature.xml file?

I'm going to check one other thing that comes to mind that is now different.

I'll check back if I find this little tidbit that comes to mind is relevant.

Thank you for reporting back.

Would love to hear from people whether this capitalization modification helps or not.
[T-Mobile Samsung Galaxy Note II] 3one7:
I did not copy the two entries from feature. xml.bak to feature.xml

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme
[T-Mobile Samsung Galaxy Note II] zuckerj:
Are you updated to the latest Wanam Xposed version?

If not, this may be another cause for Camera FC.

My camera is still functioning fine after the capitalization modification I described. I've rebooted the phone twice and still everything is working properly.
[T-Mobile Samsung Galaxy Note II] 3one7:
If 2.7.2 is the latest

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme
[T-Mobile Samsung Galaxy Note II] zuckerj:
I'm curious. Mind PM'ing me your feature.xml?

And just want to be clear, you checked your feature.xml file, that is in /system/csc/ and the to lines I referenced were ALREADY lowercase?
[T-Mobile Samsung Galaxy Note II] 3one7:
No. ... The lines weren't in feature.xml at all only in feature. xml.bak

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme

---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------

And they were lower case already. .. In feature.xml.bak

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme
[T-Mobile Samsung Galaxy Note II] zuckerj:
OH!!!

Yes, feature.xml.bak does not matter. That is the samsung's original xml file.

The file that matters is

feature.xml

Make modifications in that file and reboot.
[T-Mobile Samsung Galaxy Note II] 3one7:
Will not let me paste files to feature.xml

Jedi Master X2 G-Note 2 New Null Rom G- Gear +

Freefalling Theme
[T-Mobile Samsung Galaxy Note II] zuckerj:
As I mentioned in my initial post on this subject, you need to utilize Root Explorer option of ES File Explorer. You need to set "/" and "/system" to RW before you can modify files in the /system directory.

If you don't know how to use Root Explorer in ES File Explorer I'd suggest playing around with ES File Explorer a bit, and using Google to help you out. Not too difficult though.
[T-Mobile Samsung Galaxy Note II] 3one7:
I used es file explorer and set it to r/w I'll figure it out......phone charging now...... so xbox one for now .....thanks
[T-Mobile Samsung Galaxy Note II] dandn0ten:
hey guys im planning to update jedi x2 4.3 from jedi18 but im confused like what do i need in order to update it without any issue because i heard if i update incorrectly it will likely break my wifi function or something like that right? or do i just update it normally using the same method from jedi18?
[T-Mobile Samsung Galaxy Note II] gijoe69:
Odin flash to official 4.3 tmo

Then chainfire thru Odin> supersu> install Jedi master x2

http://xdaforums.com/showthread.php?t=2562994

http://xdaforums.com/showthread.php?t=1960784
[T-Mobile Samsung Galaxy Note II] zuckerj:
Everything you need is here:

Unofficial Official Jedi MasterX FAQ http://zuck.com/xda/JediMasterX-FAQ.html
[T-Mobile Samsung Galaxy Note II] mattlowry:
only if you want the bogus knox bootloader. I would recommend just flashing the rom and using dr ketans bootloader patch
[T-Mobile Samsung Galaxy Note II] alquistador:
Is this Rom working on Canadian carriers?
[T-Mobile Samsung Galaxy Note II] psycho4us4:
Definitely
[T-Mobile Samsung Galaxy Note II] zuckerj:
Not sure I understand... Why is the 4.3 Knox Bootloader "bogus"?
[T-Mobile Samsung Galaxy Note II] mattlowry:
1. it makes it very difficult to downgrade 2. it has a flashcounter that can void your warranty. at this point I don't believe it can be reverted

read this:

http://xdaforums.com/showthread.php?t=2570180
[T-Mobile Samsung Galaxy Note II] zuckerj:
1. What is the difficult to downgrade? Do you mean, to downgrade the BootLoader? I'm pretty sure it is always difficult to downgrade your bootloader. But downgrading ROM versions is not an issue at all.

2. I, to date, have not heard of anyone's warranty being voided due to the Knox counter. I suppose it is possible that it is happening, but not enough for me to have heard about it. Anyone know of someone who was denied warranty because of the bootloader?

But even if there are instances of the Knox Bootloader counter voiding warranties (which again, I have not heard of), there are so many ways to get around that (that have been alluded to in the forum) that I'm not really sure that should be a concern.

Anyway, neither of those items relegates the 4.3 bootloader to the status of bogus, for me anyway.

EDIT:

The link you reference says you cannot flash 4.1.x ROMs with the 4.3 Bootloader. Is this true?

I was under the impression you could flash 4.1.x ROMs with 4.3 bootloader.

If this is in fact true, then I guess that is a LITTLE bit of a strike against the ol' Knox.

But WHY would you want to flash a 4.1.x ROM anyway?
[T-Mobile Samsung Galaxy Note II] mattlowry:
no you can NOT flash 4.1.2 roms on the knox bootloader. there is a work around but I would not call it easy. take your chances with the knox warranty if you like. I will not
[T-Mobile Samsung Galaxy Note II] zuckerj:
Looks like no one in that forum was interested in my little tidbit about capitalization inconsistencies.

Just an update, my camera is still going strong.
[T-Mobile Samsung Galaxy Note II] Ash359:
Only reason I can think of is to unlock your phone.

On 4.1.1 you can do it with menus

Sent from my Jedi MasterX Note 2
[T-Mobile Samsung Galaxy Note II] zuckerj:
After doing a little research, it appears that it is easy to Downgrade to a 4.1.x ROM with the 4.3 Bootloader.

This is direct from the OP of the thread you linked:

Knox and 4.3 Upgrade Option - Post #48 [MENTION=4918502]ciphercodes[/MENTION], in summary, says, "You can flash the 4.1.x ROMS on 4.3 bootloader but ... without the 4.1.2 bootloader". Whih is exactly what we are talking about.

And here's another article.

http://www.androidpit.com/how-to-downgrade-galaxy-s3

EDIT:

I believe the AT&T exception no longer an issue.

Here's the text ciphercodes just added to his OP of the link you referenced:

Update: 02/05/2013

Downgrading of ROM's from 4.3 to 4.1.x is possible by flashing the ROM using mobile odin.

4.3 bootloader cannot be downgraded, the work-around is to flash 4.1.x ROMs excluding the older bootloader.

You will end up with a 4.1.x rom on a 4.3 bootloader.
[T-Mobile Samsung Galaxy Note II] mattlowry:
a full page of instructions is hardly what I call easy. any time odin is used I consider that difficult. not because it is hard to use but because its so easy to mess up. also your article is for the sgs3
[T-Mobile Samsung Galaxy Note II] zuckerj:
The SGS3 article was more about the concept of of going to a 4.1.x ROM from a 4.3 Bootloader.

Anyway, to each his own. Was just addressing the reasons for poor ol Knox getting a bad rap as "Bogus". ;)

I'll stop talking about Knox now so peeps don't get mad at me for cluttering up the JMX thread. (Too late!)
[T-Mobile Samsung Galaxy Note II] sabresfan:
You can flash a 4.1.2 rom on 4.3 bootloader. I've done it a few times already. No Odin involved. I also keep a nandroid of tweaked and jm18 and both restore fine.
[T-Mobile Samsung Galaxy Note II] kushXmaster:
This would be correct. There should be zero issues using 4.1 roms on the new bootloader.
[T-Mobile Samsung Galaxy Note II] pyraxiate:
I flashed back to jm18 just to test. No issues at all. I don't care if Knox has a count. Samsung isn't known to NOT honor hardware warranties because of a bootloader. They only give you hassles if the phone is inoperable due to a software error. If you flash something and Bork your phone, that's on you. They should have read and followed directions ;)
[T-Mobile Samsung Galaxy Note II] kushXmaster:
Besides the fact that you can trip knox doing a restore from kies. And I've seen quite a few people say they had their phone go in for service with no problems with knox tripped and haven't seen one person say they were denied for it. Everyone can take that how they want lol.