yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Droidriven:
If you were trying to help her understand what TWRP is then you fell way short of the mark. Answers like that only make someone more confused.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
I did lol a little on this one. Thankfully, because of awesome sites like XDA, I DO not only know that I can, I also know HOW! (Not sarcasm btw. I'm genuinely proud of that)
[Android Q&A, Help & Troubleshooting] Mablemae:
Downloading the zip now, then I'll go get the APN fix, then see if gapps will cooperate. I use Ggogle+, photos, search, and play store. Any idea if mini is what I need in gapps?
[Android Q&A, Help & Troubleshooting] Mablemae:
Trouble with this download. I clicked on the link, then on download, and this was the response. And, hey, you're pretty important with your name all over that page! I feel like I'm connected to a celebrity!
[Android Q&A, Help & Troubleshooting] Droidriven:
No, not a celebrity, lol. Just my personal AFH account where I store my files.

I don't know what is going on with the link but try this:

https://mega.nz/#!8JdVzS6K!ZAPUcBUIgoyhOKHeOPPAmpxzpZo7e3Z0968XBRPALDM

Or try this one again, I've got to see what's going on with my account, you aren't the first to have trouble downloading from my resources. They've expanded their system over the past few months and made a lot of changes, maybe they have something mixed up.

https://www.androidfilehost.com/?fid=312968873555003024

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
OFFICIAL CURRENT MOD

Universal LTE builds APN FIX - Version:*

"Universal_vmu_ApnFix-v.R1.zip"

MD5 of R2 fix:

162FCE4773D279FE37D078F09373AE37

DOWNLOAD HERE

Ok the top one wants me to download the mega app, and the second is saying the same thing as before. BUT I webt back to the original thread you sent me that led me to the apk, and I clicked and found an apk fix for VIRGIN Mobile (VM). So, I downloaded that one. Now just waiting to figure out what gapps package
[Android Q&A, Help & Troubleshooting] Droidriven:
I think that's the old APN fix(4.4.x) the one I linked was for marshmallow(6.0).

Try this

http://cloud.tapatalk.com/s/580237602ec9f/Universal_Boost_APN_Fix-R2-1.zip

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE

---------- Post added at 10:54 AM ---------- Previous post was at 10:00 AM ----------

It would go for mini, if mini doesn't work, use micro.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
That is for Virgin Mobile, correct?
[Android Q&A, Help & Troubleshooting] Droidriven:
I'm not sure, my d2spr developer buddy gave me that, I told him you had Virgin Mobile, he said Sprint didn't need this but the devices on the MVNO networks such as Virgin Mobile required the APN fix. I'm assuming that works for all the networks that use Sprint towers since they would all require the same things to use the same network.

For example, my device is a Straight Talk device on Verizon's network but TracFone owns Straight Talk, I can use the APNs for Verizon, Tracfone Straight talk, net10, Total Wireless, or Page Plus APNs and they all work because they are all for the same CDMA towers, the values aren't the same for all of them but any of them work.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
I got the 6.0 and ARM part and I downloaded the stocl and the mini ones that end with md5. Is md5 what I want, and is stock as basic as it sounds? If not md5, which one?
[Android Q&A, Help & Troubleshooting] Mablemae:
Ok was nervous because the download said "boost", and I didn't know if that was carrier specific or part of the fix name
[Android Q&A, Help & Troubleshooting] Droidriven:
No, the md5 file only verifies the contents of the gapps zip so you can be sure you got the full download, flashing files that didn't fully download can cause issues so we use a md5 sum to verify its completeness. When you download the actual apps file, it has a md5 sum in its properties, you download the gapps and the md5 file, then compare the md5 of the file you actually got to the md5 sum that it is supposed to be, if it doesn't match 100% then its not complete, something extra or something missing.

Now that that is explained, let me try to make this easier for you.

On your device, go to this link

opengapps.org

It should give you a page that looks like this.

See where I selected ARM, then 6.0, then micro?

Make your selections like that and then tap the red circle to download. I think the stock package and the mini package are too big for your device and its partitions, choose micro(I think). If your S3 is anything like mine, it won't have room in system for larger gapps packages.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
One more thing, I downloaded the fix, but it doesn't look like the other zip files and neither does the gapps. I just want to make sure I'm gonna flash them or the other option in TWRP (I can't remember what it's called, but I've done it.)
[Android Q&A, Help & Troubleshooting] Droidriven:
The APN is gonna look different because its just a few little things and not a whole system or package of app that require scripts and coding to get to the right locations.

You will be flashing the ROM+Gapps then the APN fix, not sure if its flashed along with ROM+Gapps or if its flashed after booting at least once. You'd have to ask people in the d2spr section that have done this already. You don't have to flash the md5 along with anything, its used to automatically verify the content before it flashes, if its not a match it won't flash, this is to protect your device but you don't have use it.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
I've done all that, and the download would start but never finish. So, I thought I was doing something wrong or in the wrong place. Now that I know I was in the right place, I am trying the micro to see if it works
[Android Q&A, Help & Troubleshooting] :
Try downloading in pc
[Android Q&A, Help & Troubleshooting] Mablemae:
Must've been my connection because I got it. SOOOO now im about to do this and be out of your hair for a moment. I really hope the ROM was my screen mirroring problem
[Android Q&A, Help & Troubleshooting] Mablemae:
The APN link says it is a zip file, but when I download, it isn't identified as one in my files. Also, when I go to recovery to install, it doesn't show up on my external sd in the zip or image options. When I go to the file manager, I see it on the external sd. I rebooted a few times to recovery and back, but I have no mobile connection and cannot install the APN because it's not there. I wiped and flashed MOAR ROM again in order to get here. I did get a chance to navigate the Octo ROM a bit and I'm finding it a bit difficult to navigate, but I might have been distracted by the other stuff
[Android Q&A, Help & Troubleshooting] :
Just in case.. did u backup stock rom...
[Android Q&A, Help & Troubleshooting] Mablemae:
I lost the stock ROM shortly after installing the MOAR from here. I have 2 sd cards. On one is the MOAR zip and now gapps. On the other is gapps and any new ROM I get i.e. the one I just tried. So, I still have 2 ROMS saved right now with gapps. I just need the APN. I have the link to the Octo site, so I'll look up and screenshot what I think is it
[Android Q&A, Help & Troubleshooting] Mablemae:
Pics are out of order. I followed links from OctoS page specifically

#2: on the top is the date, Aug 20, which is more recent than the R2 release on Aug 12. The bottom of the page shows the download link

#1: the actual download

#3: the files as they appear in my phone. The top is the one I had; the bottom is the one I'm talking about here

#4: what is this one? I see that they use hangouts. If I want stock messaging, do I need this, or is it specific to mms and not sms?

I'm trying to find my own answers. This is me testing my understanding and research abilities. If I know that I'm looking in the right places for the right things, then I can figure out where to look in the forums and what questions to ask when I get there. Then, you'll have your free time back to help some other poor soul
[Android Q&A, Help & Troubleshooting] Mablemae:
I have new replies. I didn't look at the name of the person until I sent the reply. I'm thankful for a second mind on this, and I'm not doubting the other person's knowledge. I'm just keeping you updated because you have a vested bit of time and interest in this and I trust you
[Android Q&A, Help & Troubleshooting] Droidriven:
That APN fix looks right.

As for the hangouts question, you'll have a normal stock messenger(its built in the ROM) and you'll have hangouts (built in the Gapps).

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
OMG I feel like a big girl now!!!
[Android Q&A, Help & Troubleshooting] Mablemae:
LTE not working, but I'm on 3g now. I will try again
[Android Q&A, Help & Troubleshooting] Droidriven:
You're missing something but I don't know what it is.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] Mablemae:
Don't stress just yet. I'm not in love yet. I like that the screen mirroring works. I hate not having a file manager that can move files from my external sd as well as having to write a folder for my titanium backups (which I cannot seem to retrieve). Basically, all the stuff 6 has to offer puts a damper on my fun on a cellular level :silly:

I am torn, though, because I like the MOAR ROM I had (aside from no screen mirroring or support). I don't want to keep using one that I can't get answers to or one that doesn't have what I want. I hate that you wet through all this. I'm going to keep looking now that I have a better idea of what I'm looking for. If you happen across anything, send to my way. Otherwise don't worry about me. I feel I've wasted too much of your time being needy and picky lol. Thank you for your help!

Oh and i think that MMS thing might have been needed because i can't send them
[Android Q&A, Help & Troubleshooting] kimiraikkonen85:
Let met ask a question about TWRP, it seems that it doesn't have an option to enable "CP Logging" for launching the phone in diagnostic mode. Do i have to go back to stock recovery for enabling CP logging?
[Android Q&A, Help & Troubleshooting] Droidriven:
No, boot to TWRP then connect the device to adb and you can capture whatever logs you need if you use the correct command.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] kimiraikkonen85:
Actually i just wanted to enable DM Diagnostic port rather than reading logs, and that only can be done in stock recovery Of Samsung as far as i read.
[Android Q&A, Help & Troubleshooting] Droidriven:
You answered your own question

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Remix Ultratablet General] tschmid:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Source Code [MENTION=5129467]tschmid[/MENTION] github and [MENTION=4964208]TerenceWSK[/MENTION] github will me merged together soon!)

Source Code (located at [MENTION=5129467]tschmid[/MENTION] github)

Device Tree

Kernel Tree

Vendor Tree

Source Code (located at [MENTION=4964208]TerenceWSK[/MENTION] github)

Device Tree

Kernel Tree

Vendor Tree

Downloads

Cyanogenmod Recovery: Not yet, have to build first :D

Cyanogenmod Rom: Not yet, have to build first :D

Contributors

tschmid

TerenceWSK

Testers

tschmid

TerenceWSK

Helpers (Initial Device Tree)

pershoot

Rom Version: 6.0.1 Marshmallow

Recovery Version: 6.0.1 Marshmallow

ROM Kernel: Linux 3.4.108

Version Information

Status: Unofficial

Created: 2016-06-01

Last Updated: 2016-06-18
[Remix Ultratablet General] lusephur:
Interesting. Is the a version of cm13 on the way? Or other custom ROMs?
[Remix Ultratablet General] tschmid:
Ill try to finish a complete cm12.1 build and if this works well ill switch to cm13 if i find the binary blobs for Android 6 or if the old blobs works with MM

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] lusephur:
Excellent. Soon as I get a chance this evening I'll charge up the tablet and fastboot flash recovery your image.

Shocking to think a cheap Teclast tablet has had more use lately due to my ultratablet being essentially useless thanks to repeated freezes and occasional reboots. Shame really, as the physical device is fantastic. (I really should grab a logcat from the device to see what's causing the freezes but I've been busy with things and I suspect the logcat may not catch the problem. )
[Remix Ultratablet General] lusephur:
fastboot flash recovery 12.1-20160531-UNOFFICIAL-sk1wg_recovery.img gives the following error output

(I have to fastboot flash as root on ARCH.)

Downloaded the image twice just to be sure it's not a corrupted file on my end.
[Remix Ultratablet General] tschmid:
I wouldnt flash it, its needing fine tuning, something is wrong with size. But you can boot it just to show someone is working on cm build

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] lusephur:
I tried flashing it,see my post above. Nowt happened. But it's a start,hopefully something good starts to come out of this.
[Remix Ultratablet General] tschmid:
Yeah have to adjust boardconfig.mk for correct recovery partition size, will fix it

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tschmid:
[MENTION=1506531]lusephur[/MENTION]

Recovery fixed, size is correct, flashed myself and voilà its working.

Proceed furter to build CM12.1 now, will update OP soon

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] lusephur:
Flashed successfully. Cheers.

Best of luck on the cm12.1,hopefully it doesn't take that long.

If you need anyone to test, I'll gladly take the risk :D
[Remix Ultratablet General] tschmid:
Cool thanks.

Try a build today, ive the device tree complete, will just controll all a second time and if it compile fine ill release it.

Source is on my github:

https://github.com/scto

android_device_jide_sk1wg

android_kernel_jide_sk1wg

android_vendor_jide_sk1wg

Ill do some kernel and device commits today,

changed a lot localy ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tomlogan1:
I, too, will test when available. Unlike TWRP or even CWM I've used in the past, the Cyanogenmod recovery does not seem to have the ability to perform a system backup. Is this something to be added or just do full backups via adb?

Thanks for all your hard work.
[Remix Ultratablet General] tschmid:
No cm recovery cant to backups, thats why i use cwm 6.0.5.1. I build it only for cm maybe is going official sometime.

As far as i know, twrp isnt posible, our device has the same limits like the Asus tf701t and there was never a twrp except a kang build. But i havent enough knowledge at the Moment, maybe after ive finished the cm build

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] _Rogue:
Excelent! Cant wait for the ROM to drop. Will flash the recovery soon.
[Remix Ultratablet General] tschmid:
Im working on it, its my first port so i've a lot to learn about cm ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] lusephur:
Take your time. It's a lot to learn and take on. There are people anxious to try it out, but only when you're ready.
[Remix Ultratablet General] lusephur:
Any update on your progress? Your github has had no activity since you posted the link.
[Remix Ultratablet General] tschmid:
Yes i havent done comits lately, im debuging a kernel issue and was in Hospital. Sorry ill update all soon

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tomlogan1:
No reason to apologize. Glad you are out of the hospital and hope it was not too serious. Insofar as your work on a ROM, we are grateful for your effort and in no way should you feel like you have to answer to anyone as to when the ROM will be available.
[Remix Ultratablet General] tschmid:
Thanks mate. Jide's kernel source is realy strange, they dont to it easy for their community to support custom roms. You've to change a lot in kernel config files only to build the recovery. Now im debugging why kernel wont Boot, maybe i need a null serial cable (usb to serial) to get some debug output to my host console (Linux).

Dont know if its serious for others and i dont know if its the correct definition in english, here in switzerland its called morbus crohn. But thanks for your support ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] lusephur:
Crohns disease is the English translation. Its not pleasant.
[Remix Ultratablet General] tschmid:
Not realy ?

Thanks for the english translation ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tomlogan1:
Thanks for this. Used it to update super su instead of supersu from kingo root. Worked great. Many thanks.
[Remix Ultratablet General] TerenceWSK:
Would you like to discuss on this?

Hi there. Ever since you publish the source code. I tried to modify it to compile CM13.0. It seems that they don't work on CM13.0. Here's some information about my experiment. Discussion and co-operation are welcomed.

Some syntax errors in /device/jide/sk1wg/sepolicy has been fixed. Besides this, several lines have conflicts with the CyanogenMod 13.0 source code, mostly in /external/sepolicy/domain.te. The source code's domain.te defines several "neverallow" rules that go against several "allow" rules in /device/jide/sk1wg/sepolicy.

Whether you change domain.te or the device tree to eliminate the conflict, the source you provided can run through compilation, but neither will boot.

My modifications are on https://github.com/TerenceWSK/cm_android_device_jide_sk1wg_sk1w , on branch cm13.0.

Also, Nvidia Shield Portable (Roth), a tegra 4 device, has bootable cm13.0 kernel and device source on CyanogenMod Github page. I compared them roughly and see no significant (vital) difference.

How's your work on cm12.1 going? I hope we can discuss on this. PM on this site is welcomed.
[Remix Ultratablet General] tschmid:
Thanks for your help. Im currently in a debug scenario about kernel and try to fix that. I compared my source yesterday with nvidia roth device and did made some modifications to my source, maybe i've forgotten a mental vendor bin/lib/etc file, kernel allways try to communicate with ft5x06 via i2c but original kernel did not init a ft5x06.

I've reorganized the hole source to reflect more the nvidia roth tree and try today a new build.

Good that you have selinux knowledge (my knowledge there lacks a lot ?)

Maybe we can work together to get cm to this device? But dont expect to much, its my first port ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tschmid:
To be precise, have a look at last_kmsg-cm.log

http://pastebin.com/rdBPpkza

and last_kmsg-orig.log http://pastebin.com/xC85PWib

There you see that ft5x06 part, but in original this doesnt happen theres a Himax init and i think thats the kernel prob.

Since ive made to much changes local should i reinit my github with your trees? After this we have the same trees and could work together?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] TerenceWSK:
That's a great idea that we work together. How do we communicate then?

Here's what I've done:

1. The Chinese Version of Ultra Tablet cannot flash the test build because of the name sk1w failed on prop check. I modified names to fit sk1w as well as sk1wg.

2. The majority of the modifications focus on SELinux.

2.1 Now the device tree has 3 versions, among them 2 were uploaded into github. All can go through compilation but what needed is a functional kernel. Good to hear your work on the kernel.

2.2 Branch cm13.0 fixes selinux problems and the branch cm13.0-NoSepolicy needs a kernel with SELinux disabled by default. Another branch grants the recovery and system block the maximum permissions to fix potential boot failure but will pollute the Android source code so it is not uploaded.

2.3 All versions of device tree failed to boot because of kernel failure.

3. One storage mount point problem has been fixed.

And if you don't mind, I'd like to know where you get those source from?

Best Regards.

---------- Post added at 04:03 PM ---------- Previous post was at 03:17 PM ----------

Yes, if you feel it convenient.

My kernel repository remains untouched, so it does not matter. If you updated your kernel source at your github, I'll re-fork or reinit mine, or, if you like to make the changes on my repository - that's ok too. Just tell me which you prefer.

My device tree will sync with every change I've made locally. But I will not send a full request to your repository untill I verify them as workable. Or if you would like to work with my cm13.0 branch (not cm13.0-NoSepolicy - not recommended), which I am maintaining now, you can reinit your github with mine.

---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------

Another notice: If you choose to work with my device tree, you should updated what you have changed 3 days ago (github shows you updated the entire device tree three days ago, and now comparison is not available). My device tree is based on your repository long ago (last month)
[Remix Ultratablet General] tschmid:
Ok, good to hear, i know sk1w is the chinese version (mine was to before i flashed a sk1wg version, buyed at geekbuying ?) but forgot that part of diffence probs (eg sk1w and sk1wg).

My source tree is originaly from [MENTION=1385883]pershoot[/MENTION] Asus Transformers tf701t since the specs are allmost the same. Kernel is from [MENTION=1319667]jide[/MENTION] github.

I think the wrong touch driver is comming from a failure in init*.rc files ill inspect that, hope i can fix this soon. Then i compare contexts files from device against mine and did made some modifigation this morning eg tv5e camera device and some more.

Should we focus our manpower on cm13 only? If yes then i reinit my tree with yours, but i also need a repo init with cm13 is that right?

Hmm we could communicare via E-Mail or hangout or do you have a prefered way?

PS ive a lot to learn especialy about git brunching, pull request and so on.

Localy ive modified my tree more to nvidia roth just to see if this tree reflect our device better.

Thanks for your help, 2gether we should bring this beast to cm ?

Gesendet von meinem LG-D855 mit Tapatalk
[Remix Ultratablet General] tschmid:
Ps i also made a new vendor tree in case i missed vendor parts

Gesendet von meinem LG-D855 mit Tapatalk