yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] scopes64:
First off, I have seen many threads on the MDA PRO (and all its variants) cutting out at high battery power levels and from what I can see there doesn't seem to be any concrete resolution. But here is my situation.

I bought a new sealed MDA Pro and immedialy flasshed to the latest T-Mobile rom. Thats where the problems began. I seem to be plagued by the MDA cutoff at 60-70% problem.

The way it manifests is the radion loses signal and cannot locate the carrier at or below 70%. At this stage a reset of the device and it reboots but as soon as you use the phone or wifi it crashes .. black screen.

As with others if I connect the USB cable and charge by PC or mains everything returns to normal. Not a very mobile solution!!

I have tried every variant of ROM out there and the problem remains. I have charged the battery for 16 hours etc etc. I have tried phone in Auto, GSM modes .. same problem :!:

The only thing I haven't done yet is buy a new battery and hence my post.

Will the purchase of a new battery solve the problem? As with other threads it would seem this came along with the latest roms. Does flashing a ROM when the battery is less than fully charged cause problems?

On a final note, if after the radio loses signal it is turned off I have been able to run the device down to 20% running videos and MP3. Is this a probem with radio levels above1.09.00 (Just thinking out loud)

HELP: This device is perfect for my daily use and having purchased a less than mobile device I am now close to getting rid .. but I dont want to :cry:

Any advice greatly appreciated... expecially from those who have fixed the problem.
[JASJAR, XDA Exec, MDA Pro General] Tron_Of_Borg:
I had this problem and a new battery fixed it.
[JASJAR, XDA Exec, MDA Pro General] scopes64:
Thanks. Look slike a new battery :)
[JASJAR, XDA Exec, MDA Pro General] stanip:
There seems to be different speculations on what causes the battery problem on the Universal: the power charge cable quality theory, one idea about the battery level stored inside the batter which some claimed to registry heck could change and another idea about the battery 500 charges limitations.

But if yours is brand new, then none of the above applies... So the refresh to a new Rom definately must have something to do with it. Wonder anybody who had bought a new replacement battery after the power drop had done another rom refresh and whether the same problem returns?

I have just bought a replacement battery (1800m Ah at standard size by MoMax which gives me another 30% more power everyday which is something good I got from paying for a new battery) yesterday to change the old one out for the same reason. Looks like until someone found the real cause, I am keeping the old one for my next rom refresh...
[JASJAR, XDA Exec, MDA Pro General] scopes64:
New Battery ... problem resolved.
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
Hi,

I am pretty new to this so sorry in advance for unnecessary questions :)

I recently installed the romaur on my D6503 Xperia z2 and think it's awesome so far.Using the doomkernel 5 at the moment and thinking of upgrading to 7.

My question: Is it safe to assume that this version (and future releases of doomkernel ) will work with romaur or should I be cautious, how does it usually work?
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
all versions should be compatible with eachother unless your jumping android versions

both doomkernel and rom aur are 4.4.2 and i see no reason at all why there will be issues
[Xperia Z2 Q&A, Help & Troubleshooting] Pesetio:
I'm assuming your using Romaur 2.2 or lower with Doomkernel 5 since that is for .69 firmware.

Doomkernel 6 and 7 is for Romaur 3.0 as it's made for .402 firmware.

You will have to upgrade to Romaur 3.0 to use Doomkernel 7.

If you want to upgrade, download Romaur 3.0 and Doomkernel 7 to you external SD card

Boot into TWRP recovery (keep pressing volume down when you see Sony logo after reboot), wipe data (dont wipe externalSD), format

Restart into recovery, you'll be taken back to CWM recovery

Flash Romaur (don't restart), flash Doomkernel, then restart
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
I see. Thank you for a great answer!
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
I can’t seem to find the 3.0 version of Romaur, looking at http://xdaforums.com/showthread.php?t=2723935 and clicking the

RomAur v3.0-link but it does not lead me to any kind of download page.

Are there som kind of place here at xda that works as a download page where i can find all the diffrent roms or am i looking at the right place:confused:
[Xperia Z2 Q&A, Help & Troubleshooting] Pesetio:
Does this link work?

https://mega.co.nz/#!dJwjkJpa!Wxsr-3PnNlAb4YzUzgmAPC9g_8tXOudOTl8-GOEpDJ4
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
Works great. Big thanks yet again!
[Xperia Z2 Q&A, Help & Troubleshooting] Xernoxis:
You also need to download the .402 fw. Don't install doomkernel v6/7 on .69 or earlier.

Sendt fra min D6503
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
Okay, so to put all of this together in correct order:

1) Flash "Kernel and baseband .402 d6503" using flashtool.

2) Download Romaur 3.0 and Doomkernel 7 and put on external SD card.

3) Boot into TWRP recovery (keep pressing volume down when you see Sony logo after reboot), wipe data (dont wipe externalSD), format (

i never realized that i had both cwm and twrp installed :eek:

)

4) Restart into recovery, you'll be taken back to CWM recovery and then flash Romaur (don't restart), flash Doomkernel, then restart.

Does that sound about right?

I really appreciate the help I’m getting from you guys.
[Xperia Z2 Q&A, Help & Troubleshooting] Mr.R™:
Sounds right to me :)
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
Hm, I'm doing something wrong. After step one I can no longer load into cwm or twrp. The screen just goes black and nothing happens when pressing either volume up or down. I have flashed back to the latest version and now all is well, except that im still on the old version :P

Any ideas for what I am doing wrong?
[Xperia Z2 Q&A, Help & Troubleshooting] Pesetio:
I never flashed the .402 firmware and baseband in flashtool or anything coming from .69 (Romaur) 2.2

I just did the exact steps i listed in previous post, except I installed advance doomkernel v04 since v06 and v07 weren't available when I flashed Romaur 3.0

Heres the link to the advance kernel, put on your SDcard in case you get a bootloop after flashing Romaur 3.0 with v06/07 kenel.

http://doomlord.xperia-files.com/download.php?dlid=WjJfRG9vTUxvUkRfQWR2U3RrS2VybmVsX0ZXLTQwMi12MDQ=

I don't want to be responsible for you bricking your phone, but the steps I listed in my previous post is exactly what I did coming from Romaur 2.2

You lose X-reality though, so flash the .402 firmware if you want to keep X-reality.
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
I restored a backup from before romaur, installed doomkernel 7.0 and then installed romaur 3.0. This seems to be working so far. How can I see if X-reality is working? I can check and uncheck the box but I am not sure it actually does anything :P
[Xperia Z2 Q&A, Help & Troubleshooting] Pesetio:
Turn on X-reality, go to album app and look at a picture, take screenshot

Turn off X-reality, go to album app open same picture and take screenshot, while X-reality is off, flick through both pictures and see if you notice a difference.

You could also upload the pics onto your PC to see if there's a difference.

I think on Romaur 3, you have to download the X-reality zip

There is no difference in mine, but I don't care since I don't have it on anways.
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
So, the doomkernel 8 is here and with it a question :P

It says that extfat won't work work this version.

How can I tell for sure if I am using extfat on my external sd at the moment?
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
Put it into your computer

Go to my computer

Right click and go to properties

You should see format type or something like that

You may posibly see, ext2 ext3 ext4 ntfs, fat, fat16 ,fat32, exfat

If it says exfat then well you guessed it! Your sd is exfat
[Xperia Z2 Q&A, Help & Troubleshooting] snaggvar:
Thank you!
[Xperia Tablet Z Q&A, Help & Troubleshooting] james_lpool:
I have just bought myself the new WIFI only versoin of the Z2 tablet, i will be selling my Z1 soon, but when i bought it from ebay, the guy told me he got it from an EE store, it is the SGP321, wifi and sim, although i have never used a sim card in it.

At the time i got it for a really good pricew, probably on par with the price of a wifi only model, but with me now wanting to sell it, i am unsure if i would need to list it as locked to EE or if its unlocked?

Is there any easy way i can find out?

Thanks

James
[Android Apps and Games] phuc_tran:
Simple but Not Easy Game : https://play.google.com/store/apps/details?id=phuc.games.hardestrps

Play the Rock Paper Scissors in a definite new game play.

Blue Team and Red Team are fighting.

And you have about 1 seconds to select which team wins : left for Blue Team, right for Red Team and middle for Draw.

Do you think it's simple?

Yes, it's really simple but your enemy is timing.
[Android Apps and Games] phuc_tran:
The game is updated to version 1.1 (fixed leaderboard loading) : https://play.google.com/store/apps/details?id=phuc.games.hardestrps
[Android Apps and Games] phuc_tran:
Got some positive reviews.

We're waiting for more downloads and comments
[Android Apps and Games] phuc_tran:
Many thanks Bwutiful. Give me rating and share this game to your friends if you have free time.

And I'm waiting for your score on leaderboard :)
[Android Apps and Games] phuc_tran:
I have just put my best score to World Leaderboard. Cheers! 50 points.

Re-post link to compete gamers : https://play.google.com/store/apps/details?id=phuc.games.hardestrps
[Android Apps and Games] phuc_tran:
We have just published new version of game : https://play.google.com/store/apps/details?id=phuc.games.hardestrps

The performance is updated already.

Let's rock paper scissors!
[Android Apps and Games] grale3:
If you added a timer above (maybe added 1 second) it would be perfect!
[Android Apps and Games] phuc_tran:
Hey, thank you very much for downloading my game :)

We have a timer bar at top (green bar).

You want a timer with number as well, right?
[Android Apps and Games] phuc_tran:
Thank you DrTrouble!

Could you please give me the link to your game?
[Android Apps and Games] phuc_tran:
Got 61 points!

Any one rock paper scissors with me :)

Try it here : http://play.google.com/store/apps/details?id=phuc.games.hardestrps
[Android Apps and Games] phuc_tran:
Hi Juvas Cheev

Thank you very much!

We will implement your suggestion soon.

Please wait.

In the mean time, keep playing game and share it with your friends.

And don't forgot post your score to leaderboard!
[Android Apps and Games] phuc_tran:
Sure. I will message you when the game is updated.

If possible, please share this game to your friends and compete them :p
[Android Apps and Games] phuc_tran:
Robert Pause and Tom Cruise are on top of Leaderboard with 89 points and 79 points : https://play.google.com/store/apps/details?id=phuc.games.hardestrps
[Android Apps and Games] phuc_tran:
Version 1.5 is living

We just published new version of Hardest Rock Paper Scissors : https://play.google.com/store/apps/details?id=phuc.games.hardestrps

Button graphics changed on press now!
[Android Apps and Games] phuc_tran:
22 players posted their score to leaderboard : https://play.google.com/store/apps/details?id=phuc.games.hardestrps

I'm waiting for more players and comments.

Cheers!
[Android Apps and Games] phuc_tran:
Updated link http://play.google.com/store/apps/details?id=digimate.me.games.hardestrps

Enjoy it! :)
[Galaxy Note Pro 12.2 Original Android Development] esgie:
At first, I am not liable for any harm or damage that may happen to your device!

If you have su and didn't trigger knox, I CANNOT guarantee that running this script won't cause 0x1!

Requirements:

1) P905/viennalte/Qualcomm based model ONLY (won't work on Exynos devices. MIGHT work on other Qualcomm LTE deices from Note Pro and Tab Pro series or even S5 / Note 3 etc - feel free to repost but give credits AS THIS METHOD SEEMS TO BE COMPLETELY NEW! ) running 4.4.2 stock;

2) root access with SuperSU (using cf-root - credits to chainfire);

3) busybox installed (I do recommend this paid installer: https://play.google.com/store/apps/details?id=stericson.busybox.donate , MOST PROBABLY free version will be more than enough, too, but I haven't tested it as I have license...)

4) Android Terminal Emulator installed ( free at: https://play.google.com/store/apps/details?id=jackpal.androidterm )

Installation:

1) download file permissive_via_kmem.sh using below link and put it in the root of internal memory (so it will be placed in: /sdcard/permissive_via_kmem.sh)

2) run Android Terminal Emulator

3) at command line, type:

su -c /sdcard/permissive_via_kmem.sh

(give it an access if requested)

4) voila.

Alternative: if u have init.d support just put the file in /system/etc/init.d to make permissive on every boot

Additional info for advanced users:

1) samsung decided to compile kernels for newer 4.4.2 roms with a flag (a kernel variable) forcing selinux enforcing mode

2) as kernel itself cannot be modified after compiled, it was impossible to set permissive mode using shell or even by repacking kernel's ramdisk, at least on Qualcomm LTE devices

3) custom kernel can do the job, but samsung's sources are broken, at least for P905, and it refuses to boot at all...

4) however, there is a workaround...

5) we cannot change kernel binary to run with different flag out of the box BUT we can obtain it's placement (address) directly in kernel memory space on running kernel and write different value DIRECTLY into the memory, hacking the kernel to make it think that the flag was different

6) for this purpose i believe we have to disable restrictions to access kernel pointers (done via sysctl)...

7) ...then read the output of /proc/kallsyms which will provide a list of all kernel variables along with their addresses in kernel memory space...

8) ...filter out a boolean variable selinux_enforcing which is responsible for all the troubles...

9) ...and write raw 00 byte into the address where the variable value is stored, via /dev/kmem.

Download:

http://www12.zippyshare.com/v/89625246/file.html
[Galaxy Note Pro 12.2 Original Android Development] cavkic:
Noob question

Could you explain to a newb what this does?

I've read this article on it and still can't fathom what benefits I'd have from changing it to permissive: http://www.androidpolice.com/2013/10/31/kitkat-feature-spotlight-selinux-defaults-to-enforcing-rather-than-permissive-other-new-security-features/

And thank you.
[Galaxy Note Pro 12.2 Original Android Development] Spere:
Check this
[Galaxy Note Pro 12.2 Original Android Development] esgie:
Well, if i'd try to express it in a simple way, from the user's point of view permissive mode is equal to selinux turned off at all, except it is logging (and only logging...) all the warnings caused by security violations, which would result in an error in enforcing mode. Permissive mode let you avoid strict security policies defined by manufacturer (and NSA - yeah, the real spies - which is maintaining general selinux rules), but also gives the possibility of establishing possible issues which may appear after switching to "really secure" enforcing mode.

And if you are asking about the exact, disturbing (ofc if security is not your main priority...) effects of enforcing mode that may affect end-users, we may start from: troubles with write-access to some (mostly external, but i have personally fought with with an issue of non-writeable internal sdcard, too) medias (well, to be honest, I do hope that my discover will help in building 100% working custom recovery...), troubles with non-working system mods resulting from bad selinux file labels, troubles with wiping partitions (ie. wiping cache or even swapping modded system lib sometimes has to be followed by triggering restorecon command on that filesystem (restore selinux context), which is leading to ie. losing root access, which may be fixed by flashing supersu again, etc etc, non working apps (especially related to modifying sensitive system parameters or resources), unchangeable system properties, unreachable functionalities, blah blah blah.... This topic had been widely discussed on xda and over the internet.

On the contrary, if you like to use your device as-is and you're not interested in modding/tweaking it, you will probably not need this mod, as you will gain nothing - but lose a little bit of security... For heavy modders, although, it's a must-have.

Btw can anyone confirm if it's working? I assume that I was looking for solution for some time, made some other changes to the environment meanwhile, so I cannot be 100% sure that above script alone is absolutely enough (but in theory it should...), however, even if it is not, it's just a matter of 1-2 days to figure out what additional, previously-well-known steps, such as running "setenforce 0", may be required in addition.

And as a brief summary: YES, my selinux is now really Permissive, both when running getenforce command and in system settings!

Wysłane z mojego SM-P905 przy użyciu Tapatalka
[Galaxy Note Pro 12.2 Original Android Development] RaSand:
After following all steps getenforce still returns enforcing and in system it also shows enforcing.

If I try running setenforce I get permission denied.
[Galaxy Note Pro 12.2 Original Android Development] esgie:
Ok, can you enter:

su
printf '\x00' | su -c dd of=/dev/kmem seek=$( printf '%d\n' '0x'`cat /proc/kallsyms | grep ".*\ selinux\_enforcing" | cut -f 1 -d " "` ) bs=1 count=1 conv=notrunc

into terminal and tell me what's the output and/or the enforcing state??

Wysłane z mojego SM-P905 przy użyciu Tapatalka
[Galaxy Note Pro 12.2 Original Android Development] RaSand:
As requested

Output:

/dev/kmem cannot open for write: permission denied

getenforce still returns Enforcing

u0_a286@viennalte:/ $ cd /dev

u0_a286@viennalte:/dev $ ls *mem*

ashmem

kmem: Permission denied

mem: Permission denied

ramdump_audio-ocmem

ramdump_smem

smem_log

1|u0_a286@viennalte:/dev $

Same result in # mode
[Galaxy Note Pro 12.2 Original Android Development] RaSand:
u0_a286@viennalte:/ $ su

root@viennalte:/ # ls -lZ /dev/kmem >/sdcard/info.txt

/dev/kmem: Permission denied

1|root@viennalte:/ #

info.txt is empty

chcon: Could not label /dev/kmem with u:object_r:device:s0: Permission denied

2|root@viennalte:/ #

waiting for code for 3)

same result in step 2 with added remount

---------- Post added at 04:55 PM ---------- Previous post was at 04:30 PM ----------

It swallowed all commands in 3) BUT re running the script didn't change anything. After please wait.... done it still says selinux is set to Enforcing. Sorry.

getenforce returns enforcing

setenforce to 0 or Permissive doesn't change a bit.

seems it has to be done the hard way

better luck next time
[Galaxy Note Pro 12.2 Original Android Development] esgie:
Your errors are quite strange, as it seems that you don't even have permissions to check the simple content of a directory...

Try to run commands from step 1 - 3 again, but with slight modifications (below), so theyll run in separate, undoubtly-rooted shell... Test also with modded command (you can try it alone before in the very beginning...)

Also: please run 2 and 3 in reversed order, ie. first step 3 and if not working, without rebooting, run step 2...

Btw are you using SuperSu 1.99? If no - after trying all below options, upgrade SuperSu from the Play Store, run it to update the binaries, reboot. check commands again. If still the same, install update to /system using option from its menu (it will do some cleanup and ask to reboot, after that you have to run option again, this time it will perform installation, after which you have to reboot again - after boot run SuperSu and check if the option is greyed out, if yes, everything went fine) and check all steps once again...

Here we go.

Main command:

su -c printf '\x00' | dd of=/dev/kmem seek=$( printf '%d\n' '0x'`cat /proc/kallsyms | grep ".*\ selinux\_enforcing" | cut -f 1 -d " "` ) bs=1 count=1 conv=notrunc

Step 1 v2:

su -c ls -lZ /dev | grep kmem >/sdcard/info.txt

Step 2 v2 (formerly step 3 ):

su -c busybox mount -o rw,remount /
su -c sed -i "s:^.*\/dev\/[k]*mem.*$::g" /file_contexts
su -c setprop selinux.reload_policy 1
sleep 3
su -c restorecon -R /dev

Notice: I am not sure if setprop selinux.reload_policy 1 is enough to force sammy's android (which is a really giant b***ch to hack when compared to any other android...) to reload the policy, this may really work, but only if the policy is reloaded on-line using new defaults. Later I will look for that information...

Step 3 v2 (formerly step 2 - please run directly after step 2v2, without rebooting...):

su -c busybox mount -o rw,remount /
su -c chcon u:object_r:device:s0 /dev/kmem

Notice: step 3 - when ran fine - might now print some errors that it cant access some stuff in /dev - this is absolutely ok. But formerly I disabled the output at all (not to confuse you with some strange errors), but it resulted in lack of possibility to find out if the command ran AT ALL or if it escaped because of no permissions on the very beginning.
[Galaxy Note Pro 12.2 Original Android Development] RaSand:
Before we go on here let's get a few things out of the way.

1) please advise where i should get supersu 1.99 from. I'm on 1.94 and in my country (GE) there is no newer version available in the play store.

2) first thing I usually do when I start the terminal is type "su"

3) I'm an old man. So please be patient

that said let's give it another try

---------- Post added at 06:42 PM ---------- Previous post was at 06:11 PM ----------

This is starting to test my temper. I guess I will put the steps into files and run them with gscript. Hang on. Might take some time

---------- Post added at 07:30 PM ---------- Previous post was at 06:42 PM ----------

Guess I had it for today. No changes whatsoever.

Here is what I did

installed supersu to /system. Option is greyed out now

made a new script for every box of code. Main and step 1 to 3

Made copies and added some echo lines so I could see if scripts work and/or finish correctly

executed scripts with gscript in the given order

No echo in step 1 to 3

ran original code

same result.

don't know what else to try.

sorry
[Galaxy Note Pro 12.2 Original Android Development] RaSand:
Just done flashing twrp and supersu(now 1.99)

i will not give up that easy, don't worry.

Just to be on the safe side i downloaded b4. Maybe you should remove it for the moment.

Looks like fun being the most important part of the team.lol.

btw. Knox was tripped about 2 hours after i got the device

busybox is v1.22.1 (2014-01-25 17:27:18)

---------- Post added at 10:05 PM ---------- Previous post was at 09:15 PM ----------

This it what happened after the last command in step 2 was executed

Could not label /dev/cpuctl with u:object_r:cpuctl_device:s0: Operation not supported on transport endpoint

Could not access /dev/kmem: Operation not supported on transport endpoint

Could not access /dev/mem: Operation not supported on transport endpoint

Could not label /dev/pts with u:object_r:device:s0: Permission deniedroot@viennalte:/ #