yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Matt07211:
[MENTION=5915971]spalnndsstest[/MENTION]

Can you please try this and report results.

Requirements:

Root

SQLite Editor

Steps:

1) Open SQLite Editor (grant root when requested), scroll down to "Settings Storage", click it.

2) Once inside "Settings Storage" click "System"

3) Once inside "System" scroll down untill you find "notification_panel_default_active_app_list"

4) Edit the record and add

TouchSensitivity;

Onto the end of the string of words found in the "value" record.

So on my one it would look like (yours may differ)

Wifi;Location;SilentMode;AutoRotate;Bluetooth;MobileData;UltraPowerSaving;WiFiHotspot;Nfc;Sync;DormantMode;AirplaneMode;TouchSensitivity;

Save and exit the app.

5) Go to notification shade and go to the edit the layout area, once inside clock reset. You should hopefully now see the button.

Refer to the screenshots for more guidance.

Please report if this works or not.

===

Status Update about this device.

Kernels: [MENTION=4379858]IXgnas[/MENTION] Is working on the xcover3 Kernel (Happening slowly as the CPU used is rather uncommon and therefore we have no examples to base of so it's really trial and error) [MENTION=4885288]help3r[/MENTION] Is working on the xcover3 Value Editon Kernel (he going rather fast now that he's managed to compile and boot his first custom kernel, should hopefully see a realse of this around February 1st)

ROM: [MENTION=6318002]Matt07211[/MENTION] (Me), Currently in the process of porting. Started on Xcover3 (uncommon CPU so is a bit more difficult). Haven't started on xcover3 value editon yet :(

TWRP for Lollipop: [MENTION=6318002]Matt07211[/MENTION] (Me) and [MENTION=7848003]Sonof8Bits[/MENTION], currently waiting for somof8bits to come back from holiday or when I finish porting the necessary stuff (Which ever comes first)

Misc:

- I currently gotta redo the post 2 with better instructions for people looking to build for this device.

Hopefully you should see some development by the end of the month.
[Miscellaneous Android Development] spalnndsstest:
thanks

i need to root the phone yet, i will read the manuals soon, hopefully i will not brick anything, as it scares me a little bit.
[Miscellaneous Android Development] Matt07211:
In my honest opinion, Samsung devices are probably the safest to root. Cause it's always got a persistent method/service (Odin) available. And since it doesn't get overwriten when flashing and it's read-only, you can be 99% sure you can always recover the device.
[Miscellaneous Android Development] sasbionage:
Invalid apk file?

Hiya, i have followed instructions closely but get this "invalid apk file" msg after install superuser command,

Any suggestions pls? tia.
[Miscellaneous Android Development] Matt07211:
I suggest you redownload the file again. Sounds like a corrupt file.

Can you tell me, is the SuperSU.apk you are using the one provided in zip file (I've personally tested it) or is it from another source?

Edit: or just downloaded the one from Google Play. Exactly same program, just you get easier updates
[Miscellaneous Android Development] sasbionage:
Thanks for your reply, yes, the supersu file was the one you provided, i have re downloaded but am still getting the same message
[Miscellaneous Android Development] Matt07211:
Just install the one from play store
[Miscellaneous Android Development] sasbionage:
All working fine now thanks,

My problem was a dodgy usb port on laptop, tried another port and bingo!
[Miscellaneous Android Development] Matt07211:
Haha. Glad you got it fixed.
[Miscellaneous Android Development] sasbionage:
Am i right in thinking a customised rom would be a set up that has most of the bloatware removed, system tweaks and some usefull apps pre installed?

If so can somebody share me a link to download one to try pls?

(Sorry if this should be in a seperate post,)
[Miscellaneous Android Development] IXgnas:
We're currently working on one. Since it's AOSP, it will have no bloatware. We haven't built it yet.
[Miscellaneous Android Development] sasbionage:
Ok thanks
[Miscellaneous Android Development] Matt07211:
Yea that and a custom ROM, sorry it's going slowly but I procrastinate to much. Hehe. But I'm finally getting my but back into gear and get back to working on the ROM.
[Miscellaneous Android Development] Devhost97:
Custom Kernel for Samsung XCover 3 VE - SM-G389F is here:

https://xdaforums.com/android/development/kerne-devhost97-kernels-fresh-look-t3546787
[Miscellaneous Android Development] Matt07211:
Adding to OP. :)
[Miscellaneous Android Development] endbored:
Anyone else having problems with apps like titanium backup and adaway not recognizing root? I already used the code from starting post in terminal but that didn't work and I don't know why. The Emulator has root access. Super sU is latest 2.79.

edit

I'd also like to see a custom rom. If possible plz make it menus black/dark so it's eye and power friendly or maybe even customize able. I really don't like these bright and ugly looking menus.

Best regards
[Miscellaneous Android Development] Matt07211:
Yea, after a few days uptime, trying to get root doesn't always work. A reboot and it works again.

I believe it's in relation to Samsungs anti-root features, securitylogagent.apk and Knox. I have yet to have a proper look into that.

As for you rom request, depeds on the code implemented by lineageOS/OmniRom or how much I care about the feature to try and have a go at implementing. Basically I'll see what happens when I arrive at that point of rom compiling.
[Miscellaneous Android Development] IXgnas:
G388F custom kernel (made by me): https://xdaforums.com/android/development/kernel-dixcovery-kernel-t3547128
[Miscellaneous Android Development] Matt07211:
Added to op
[Miscellaneous Android Development] endbored:
For me it's not like this. F.e. titanium backup and adaway never worked with root. Tho there's other apps that work fine with root all the time and I dont need to reboot.
[Miscellaneous Android Development] Matt07211:
I can safely say that these 2 apps in particular work on my device. And both of them are built/have been upgraded to be systemless root compatible. So I geuss it comes down to what I mentioned Earlier. So I gotta look into Samsungs anti root, know and securitylog agent
[Miscellaneous Android Development] Matt07211:
Anyone else on here experiencing bad battery drain?

I think I might have a fix for it. Just gotta test it :)
[Miscellaneous Android Development] Devhost97:
Hello guys,

If anyone use My Custom Kernel for XCover 3 VE (SM-G389F) - please update to newest version ! They have improved perfomance and fixed some bugs !

https://xdaforums.com/android/development/kerne-devhost97-kernels-fresh-look-t3546787
[Miscellaneous Android Development] IXgnas:
You already made your announcement, no need to repeat it.
[Miscellaneous Android Development] Fred4807:
Hello All,

I have few basic questions on system update and stok rom upload :

> what is exactly loaded when I put the phone in download mode and and send a Rom via Odin (AP) ? The rom on the hard drive is +2Gb. The transfer is done in around 3 minutes. I can't imagine all the 2 Gb have been uploaded in 3 minutes. Maybe I am wrong and everything is uploaded ; but formerly I had a S3 mini and upload was very long

> If not everything is uploaded, how can I force upload of the entire Rom. Which option have to be selected in Odin ?

Backgroung of the question : on SM-G389F : In some case (after app install, MMS download, app opening or even call receive...) the screen become black, like in stand by (power button press). It last 15 or 20 seconds, then everything come back to normal.

This issue has always been on the phone, even before rooting, and with CSC XEO and XEF (the 2 tested). I would like to reload entirely the Samsung Rom in order to try to solve that.

If I don't manage to solve the issue by stock rom upload, I think I will request help from Samsung via app like "smart tutor", but in that case I will have to remove cleanly root, twrp and upload original rom (XEO)... :rolleyes:

So if you have any suggestion...

Thanks for your help !
[Miscellaneous Android Development] IXgnas:
When you upload the firmware via AP, everything on your phone (excluding external SD card) is replaced with what's inside the archive. 2 GB is not that much, considering USB technology is getting faster and faster.

I don't know what's the problem with black screen, but you can try flashing other region's ROM to fix it (I can't help you on that matter since I've only encountered that problem on Galaxy S2).
[Miscellaneous Android Development] Matt07211:
What? This phones got a relatively small user base on XDA so I don't mind him posting in this thread about the kernel

Let's start with the first part of your post :)

I'll just give you a quick rundown of the whole process, it should give you a better understanding, if you don't get what something means ask me or go research the term.

Background (needed to explain about ap button) of the firmware file.

Once you finish building etc.etc. you get out image files (.IMG), if you look inside the firmware package you'll see stuff like system.img which goes onto the /system partition, boot.img which goes to the /boot partition, pretty straight forward.

Now to make this a flashable package for Odin you tar these files (.tar) (think of it like a zip file). They then generate a md5 hash (a string of letters and numbers, e.g. Eha2oqw8202ajs...., That helps verify the integrity of the data) and add that onto the end of the tar file. So the extensions on the end of the firmware look like this (firmware.tar.md5).

Now when you load the ".tar.md5" file inside Odin via the AP button the program also generates a md5 hash of the file and compares that to the value that was added onto the end of the tar file earlier, if they match, you get the okay to flash, if they don't then then the file is corrupted and the hashes don't match.

So, basically the couple of minutes it takes is because it's generating a hash of the file, not copying it to the phone.

When you click start, that's when it flashed the files to the partition, and it takes a lot longer then the last step as it's writing the data onto the phone.

Hopefully that helps you get a clear picture of the firmware file and Odin.

As for the second part of your post, I can say I experience that to (on the SM-G388f) and I believe it's kernel related. I also experience scroll flickering (kinda fkiekrs up and down Ike's it's being slightly scrolled in one direction and then back down), I also believe this is kernel related (Note I have experienced this ony relatives phone as well which is a cheap low end pure asop phone, this means it's just not limited to our devices)

Sorry for the wall of text
[Miscellaneous Android Development] Fred4807:
Thanks both of you for explaining me the upload process in detail.

(Matt, don't worry about this wall ! Yours is a lot less frightening than the another one popular in the US these times... ;) ... and learning reply are always welcome ! )

for the black screen I have contacted Samsung by phone today ; I will bring the device tomorrow in their repair shop. Will post if I get any explanation on the issue. Hope all evidence of rootings have been correctly cleaned... :rolleyes: My only concern is in download mode where I read "WARRANTY VOID : 1 (0x0304)" ; think this was set to "0" before rooting... otherwise the other fields shows "official"

Fred
[Miscellaneous Android Development] Matt07211:
Hehe.

Yea that warranty void got tripped when rooting, it may or may not make a difference with the warranty, it all depends on the person you take it into.
[Miscellaneous Android Development] NamelessXXV:
port cm

port lineage os to i9305 please
[Miscellaneous Android Development] Matt07211:
Sorry dude your in the wrong thread, your looking for this one, https://xdaforums.com/galaxy-s3/development-i9305

I'm only supporting SM-G388f and SM-G389f
[Miscellaneous Android Development] IXgnas:
Port newest MIUI to G388F please.
[Miscellaneous Android Development] Matt07211:
LineageOS First.

Once the device repo goes up, feel free to fork, modify and create a pull request with the needed changes for MIUI rom.

IMHO, I don't like the look of MIUI much.
[Miscellaneous Android Development] IXgnas:
I was kidding, geez. If he wanted us to port LineageOS to his device, he/she/it should port a ROM to our device.
[Miscellaneous Android Development] Matt07211:
Lol. Geuss that's ain't gonna happen.
[Miscellaneous Android Development] IXgnas:
Why would it? AOSP first, our own custom ROM second, LineageOS third (though that's unlikely)
[Miscellaneous Android Development] Matt07211:
LineageOS is just like pure ASOP with some "love mixed into it"

Custom built ROM seems unlikely but.....
[Miscellaneous Android Development] IXgnas:
But we'll do nonetheless. Don't be a p****, we can do it.
[Miscellaneous Android Development] cakemaker:
Thanks for doing this guys!
[Miscellaneous Android Development] Matt07211:
No problem :)

I can be what I want to be /s
[Miscellaneous Android Development] IXgnas:
Fine, be sarcasm.
[Miscellaneous Android Development] IXgnas:
You didn't have to put that much effort into that comment. Flashing stuff is the same on all platforms.
[Miscellaneous Android Development] oneyb:
not quite

It's for me 3-days ago. And no, it's not the same. JOdin3 is difficult to get for linux (I couldn't, I had to get it for mac, but that still works), the twrp image depends on which xcover3 you have, and one has to stitch all this together - costing one time. Furthermore, the difference between a brick and a bad ass, pocket-sized touchscreen computer is in the details.

It is a bit overboard, but documentation is helpful for the less-versed (for me from 3 days past). :cyclops:
[Miscellaneous Android Development] IXgnas:
I'm saying that some parts of your and Matt's tutorial match, so there was no need to reinvent the wheel.
[Miscellaneous Android Development] Matt07211:
I'll update OP when able to, on how to use Linux/MacOS equivalents of Odin (Heimdall, JOdin3, or running the app through Wine).

There isn't any reason to flash SuperSu on the SM-G388f as it's unable to unpack the boot.img and will throw an error, with that being said I should probably ask Chainfires to update his unpack tool to include support for this. And if your on SM-G389f then I won't recommend flash the boot.img (Phones have different SoC) or the su.img (2 Device specific files are used, and are incompatible with each other.

I'll update Post 3 with fdroid link and your listed apps later today when I get the time to (Need to format it better).

Thanks for pointing out that this guide lacks Linux/MacOS support. But that being said most Linux users now how to Google to solve there problem, like you did:highfive:
[Miscellaneous Android Development] Matt07211:
Hey everyone,I've almost finished the initial device port, once I've finished that, im gonna test how well it is by building LineageOS, so I'm gonna need some tester's in the near future ;)

So keep your eyes on this thread.

--- [MENTION=8058953]oneyb[/MENTION] I have still yet to add the info for Flashing via Linux, just posting to say I haven't forgot, I've just been wrapped up into trying to finish the device Port.
[Miscellaneous Android Development] oneyb:
no worries and that sounds interesting

Looking forward to it. Thanks again for all this info!
[Miscellaneous Android Development] Matt07211:
Device tree is online, https://github.com/Matt07211/android_device_samsung_xcover3lte , I've still gotta do some thing's, but custom ROMs are almost here. Once I can compile TWRP with this device tree and do 2 other repos then it should be ready for compiling ROMs. So gonna need tester's for that soon.

---

Side note, a new xcover is coming out, http://www.phonearena.com/news/Sams...ecs-reveal-Exynos-7570-chipset-inside_id91010
[Miscellaneous Android Development] IXgnas:
Ads are getting smarter :D.
[Miscellaneous Android Development] spalnndsstest:
i cant understand why the xcover does not comes with gorilla glass, its a phone made to survive, so makes sense to add gorilla glass,

first time i move out to the street, got a very tiny little mark in the screen.

Any way, i think there is an error in the 389 (android 6.0) version,

when i try the front camera, i shot a picture and then the picture is saved but mirrored! tried to find how to disable this but i see no option...

you guys have the same problem?
[Miscellaneous Android Development] Matt07211:
Gorilla Glass, it's a mid-range phone so you can't expect everything.

I don't get what your talking about with the camera
[Miscellaneous Android Development] spalnndsstest:
lets say i hold my right hand up when making the selfie with the front camera,

in the screen (preview) it looks normal, like looking a mirror,

but once i shot the picture, is saved and the result looks like my other hand is up, image is mirrored,

it does not save the same picture as the preview, like it does when taking the picture from the back camera,
[Miscellaneous Android Development] Matt07211:
Oh, okay.

Go to camera app click the settings icon, you should see a thumbnail that looks like the vase/face optical illusion. Click that. This setting saves images as flipped. I've tested it. When off the problem you describe occurs. When turned on the image is flipped and saved as it is shown in the camera preview.
[Miscellaneous Android Development] spalnndsstest:
thanks,

i dont have the thumbnail you talk about, maybe a VE diference, but it was there an option for save it as in preview,

it really came up unnoticed to my view when looking for all options, thnks
[Miscellaneous Android Development] Matt07211:
See be second bar hanging below the main top bar. The first icon there is what I'm talking about.

Note: It may be an option not on display, click the menu button on the far right to see more options, it may be hidden in there
[Miscellaneous Android Development] spalnndsstest:
i see, in the VE edition its clearly different,
[Miscellaneous Android Development] Matt07211:
Not even in any sub menu? Looked through all sub menus? Tried every button?
[Miscellaneous Android Development] spalnndsstest:
yes, the option is there, but they removed the icons and when you click the top left "circle", appears a fullscreen list of "on/off" menu options, its just idfferent design,

for your curiosity, here is how it looks in VE edition

[IMG="http://i.imgur.com/WLM0puA.png"]http://i.imgur.com/WLM0puA.png[/IMG]
[Miscellaneous Android Development] Matt07211:
I don't know Spanish but I translated a few of the options in the image, could find it. But one last try, have you hit the arrow on the top right of the image?
[Miscellaneous Android Development] spalnndsstest:
my friend, maybe i was not clear enough, but the problem is solved since yesterday,

its one of the options in the list,

i was just showing you how its the new user interface,

regards!
[Miscellaneous Android Development] Matt07211:
Oh, awesome. :)

Sorry I dont read/speak Spanish and only translated some of the options, and hadn't realised it was one of the untranslated one.
[Miscellaneous Android Development] Devhost97:
Here you have
[Miscellaneous Android Development] Devhost97:
Sorry for double post - i uploaded it via XDA app
[Miscellaneous Android Development] Sonof8Bits:
Just wanted to say I recommend Open Camera. It gives you way more options than the build-in camera app allows. Stuff like more scenes and higher resolution. Suddenly I can make 1080p movies on my phone where the Samsung app only allowed 720! :D

Mind you, this all depends on the camera and this isn't true for every device. But now that I'm used to this one I'm not going back to stock!

OK, enough off topic for now...
[Miscellaneous Android Development] spalnndsstest:
will give a try, thnks
[Miscellaneous Android Development] Devhost97:
This is real 1080p recording or interpolated?
[Miscellaneous Android Development] Sonof8Bits:
To be honest, I don't know. But it makes editing video a little easier for me (combining action cam video with phone files).
[Miscellaneous Android Development] spalnndsstest:
i just bought a few NFC keychains at ebay

but the phone just says "NFC not compatible"

any idea about what might be the problem?

NFC Tools app says its a " nxp mifare classic 1k - not supported"
[Miscellaneous Android Development] Matt07211:
Do you mean the NFC tags are not compatible or the NFC on the phone ain't working?
[Miscellaneous Android Development] spalnndsstest:
NFC works perfectly, i tried with my credit card, and with some ebay NFC stickers,

but now i am trying with some ebay NFC keychains, and those ebay keychain tags looks like dont want to work

with the phone, wondering whats wrong with those tags, i have 5 and all 5 return same error/problem,

NFC Tools APP know there is a tag but can't work with it, when he detects it it return this reading: "nxp mifare classic 1k - not supported"

and the phone itself when detect the tag says "NFC tag not compatible"

i guess there is nothing i can do,
[Miscellaneous Android Development] Matt07211:
Geuss there isn't much you can do about it. If it's not compatible, not much you can do if hardware related, but if software related then wait for my LineageOS ROM that should be completed soon.

I'm not really well versed in NFC do I can't really help :(
[Miscellaneous Android Development] praun:
Hi,

Does anyone know if we can enable adoptable storage on the xcover3?

And/or if this method for the s7 also works for the xcover3?

https://youtu.be/VDLOAzWwd-M
[Miscellaneous Android Development] Matt07211:
Adoptable storage was introduced on Marshmallow (6.0+)

So:

xCover3: No adoptable storage

xCover3 Value edition: Yes, but not as simple as normal/pure ASOP, believe it requires the use of ADB.

Paging [MENTION=4885288]Devhost97[/MENTION] for how to do this, cause I remember him mentioning how to do it.

I didn't watch the YouTube video so I can tell the validity of the instructions.
[Miscellaneous Android Development] Devhost97:
[MENTION=784782]praun[/MENTION]

Yees it was working with guide from this video. When i get some time i will mount and upload the video with guide for XC3VE.

Stay tuned.
[Miscellaneous Android Development] Matt07211:
Cool, I'll update OP when you do.

Same with you [MENTION=8058953]oneyb[/MENTION] I haven't forgot to update OP I just haven't gotten around to it
[Miscellaneous Android Development] ash1970:
I need stock kernel G388f , someone help me?

Wysłane z mojego SM-G388F przy użyciu Tapatalka
[Miscellaneous Android Development] ash1970:
Wysłane z mojego SM-G388F przy użyciu Tapatalka
[Miscellaneous Android Development] Matt07211:
Oh my fault, I Haden't noticed the "ve" in the end of the link, indicating that it was the value edition version of the phone (I belive the only difference between the two phones is, I belive (I have no proof as I haven't looked into the value edition version yet, is that the system partition is bigger allowing for marshmallow to fit into the system partition. In the normal edition, we have only 200 megabytes left after lollipop update, so probably not enough for Marshmallow. Other then the slightly different partition sizes I belive that the two devices have identical hardware)

I was referencing this version (https://twrp.me/devices/samsunggalaxyxcover3.html) when I said it wasn't working on lollipop, so I wonder if your value edition TWRP would work on the lollipop version (gonna test it later tonight)

Will update the OP with the relevant information/links with credit to you.

As for root on this device I am currently working on it (albeit not my full attention with both work and exam revision gaining most of my attention at the moment, my exams finish on 26 October, so it then will have my full attention until then this isn't of high priority)

My only road block is getting the boot.img to boot once flashed with Odin, which it isn't at the moment, not sure what security they have in place, but hey I will still keep trying till I get it.

Note: for anyone wanting the write-up I mentioned in a earlier post, I haven't had much time to work on it so it's slowly being written up. ;)

Sorry for the wait