yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] social-design-concepts:
in my experiments i've been using the kernel from the boot image that goes with the android builds and just modifying the init scripts / build.prop to work for my device , though the dell is alot more generic , gonna test lollipop tonight to see if i can get it to boot the asus build. I think it might come down to is using parts from a device built off of the same product reference platform.
[Galaxy Tab 3 General] Hazou:
If you really talk about the GPU then it could be used. As long as the same kernel source of the gpu side is used yes ;)

I also found out that the google_diffs don't include all patches from 4.4.
[Galaxy Tab 3 General] social-design-concepts:
Really wish a leaked redhookbay bsp would surface
[Galaxy Tab 3 General] xTear:
[MENTION=6587211]nels83[/MENTION]

Could you post some screenshots? or an video how it works and looks
[Galaxy Tab 3 General] nels83:
Sure. Here are some screenshots. I tried to record a video but it seems there is a problem with the Intel.AVC encoder... I'll try again later.
[Galaxy Tab 3 General] r2d23cpo:
This is nice. Good job, I am downloading to do a test ride.

"fugu is x86." What is fugu code name for?

Do you have any Idea of how many Gigbytes you downloaded from "AOSP repo of android-5.1.0_r3" + your git hub files? I am interested but the fact that my Internet is not reliable makes it difficult.

Yes PLEASE. Listen CM is the corner stone for many other projects. So I definitely will like to see CM12 tree also open other possibilities like touch Ubuntu etc. I hope others come and ask. Angels CM tree is about GT-P5200 and this is GT-P5210.

Here is where I get confused.

It is not true that Anything over 4.4.2 is "SELinux Enforce". How is that you say "SELinux (disabled in kernel for now"?

In fact I been saying that Android end time is coming soon! Just because I thought that we could not get rid of "SELinux Enforce" and all its complications. Can you correct me me if I am wrong?

I see [MENTION=6109572]xTear[/MENTION] is here. So I hope [MENTION=5707708]Jacker31[/MENTION] see this he was pretty interested in compiling CM, I guess you git will help him in GT-P5220 tree.
[Galaxy Tab 3 General] Jacker31:
Hmm.....I wish I could help but I paused my development as i only have 1gb left on my pc to spare. I am currently waiting for my new I7 laptop to arrive, hopefully i can get it on first of may :) I do hava a git for p5220 but give me some time to dig out from my files... *dislocated it lol, it was a mess....*
[Galaxy Tab 3 General] nels83:
Sorry. I meant that fugu (codename for Nexus Player) is an officially supported device in AOSP. And since it is based on an Intel processor, it means a lot of work for x86 has been integrated upstream.

The .repo folder takes 19GB and yes it took a looong time to download... Good news is that it can be stopped and resumed.

To be honest I wanted to try anyway ;) I will try to make something like what's been done for p5100/p5110 or i9300: a common repository with only variations for p5200/p5210 (maybe p5220). However I will only work on p5210 since I don't own a p5200 and don't really know how to handle the gsm stuff for this device.

I really don't know. SELinux caused me troubles so I disabled it at the kernel level and planned to integrate it when everything works.

That's the purpose, trying to help for once ;)
[Galaxy Tab 3 General] nels83:
CM12.1

Ok, release early, release often...

You'll find cm-12.1-20150413-UNOFFICIAL-p5210.zip in the CM-12.1 folder on androidfilehost.

It's really quick and dirty but indeed CM does a great job. Did not see any FC so far and everything seems to work quite well (no audio, no camera and no vibrator of course).

This is from my "experimental" common repository. I hope I'll be able to clean this and upload it to github by the end of the week (I'm not forgetting p5200).

Have fun!
[Galaxy Tab 3 General] r2d23cpo:
I downloaded AOSP but have not tested. I will download cm-12.1-20150413-UNOFFICIAL-p5210.zip And see if I can backup and test both. You are quick. Nice job. I have not check but do not forget One thing I am interested is your CM12.1 tree for P5210. Angel_666 sugested me, that Ubuntu Touch could be a nice asset in the route to get a useful Linux distro running natively in P5210! Please forgive me if I am hijacking. I guess is a useful thought.

I still confuse as if it possible to disable SELinux Enforce! I guess what is the "ENFORCE" meaning!

Regards, P5200 and P5220. I bet Angel_666 can help in P200 tree, and I know for sure a few will jump in for P5220 tree. AOSP/CM has been the desire of many here.

As regards on "no audio, no camera and no vibrator".

Audio is a must, to be able to stream multimedia.

Camera. for me I can live without it, Well I do use it to transfer quick Web Address via QR Code on my Firefox

---------- Post added at 09:57 PM ---------- Previous post was at 09:16 PM ----------

@nels83

Listen I just downloaded "cm-12.1-20150413-UNOFFICIAL-p5210.zip".

I see is in a Update.zip format! Nice. Can you tell me if CM build tree created as default this update .zip?

Any way, any special procedure for installation?
[Galaxy Tab 3 General] :
nels83,

hi, just posting your github link https://github.com/nels83?tab=repositories

looks neat! i have got to get another tab.

m
[Galaxy Tab 3 General] r2d23cpo:
[MENTION=5864662]moonbutt74[/MENTION]

Nice to see you around.

[MENTION=6587211]nels83[/MENTION]

Can you post the generated recovery.img done by CM12.1?

---------- Post added at 11:44 PM ---------- Previous post was at 11:28 PM ----------

[/COLOR [MENTION=6587211]nels83[/MENTION]

AOSP-I guess I do install boot.img & system.img. I guess I will clean all cache/data in TWRP and install it by creating a ZIP with updater-script like.

ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p5210 ");
ui_print("Flashing AOSP5.1-P5210");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("boot.img", "/dev/block/mmcblk0p10");
#
ui_print("Flashing SYSTEM.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("system.img", "/dev/block/mmcblk0p8");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");

then install houdini, then google store

CM12

You said to ad Houdini to AOSP. Do I have to add it too to CM12?

---------- Post added 14th April 2015 at 12:32 AM ---------- Previous post was 13th April 2015 at 11:44 PM ----------

So my updater-script(previous post) did not work. system.img failed to mount after installation.

I use TWRP to Format DATA + Factory reset.

I guess I have to create an ODIN tar.md5 for system. I will do that latter.

I then try CM12 and took some time to boot, just showing Blue CM Android Head. But It finally got it working. I install houdini + google sore. I guess I need to install root too.

Yep, no sound and camera failed.
[Galaxy Tab 3 General] xTear:
So this means the rom got still the same errors like the CM-Build from Angel?

I Hope that somebody got the sound/vibrator working (never used the camera lol)
[Galaxy Tab 3 General] LegendSmoker:
Where are these 2?

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy Tab 3 General] nels83:
In the Extras folder above the CM-12.1 folder on androidfilehost.
[Galaxy Tab 3 General] xTear:
Does this mean that the camera works?
[Galaxy Tab 3 General] r2d23cpo:
I spent some time yesterday backing up, testing CM12 and installing my usual apks.

First thank you for this opportunity. This is the first time I see and play with A 5.1. The OS seems pretty good and I like the graphics. Nice work in you implementation for P5210.

But I have to say the following even thought it has nothing to do with your work, but Android 5.1. Let me explain. You see, I am against the all new security stuff been implemented on all Android version over 4.3 well even 4.2.2 but I can not do anything and get 4.1 since we never got that version. You see Goggle, Samsung and Intel are following N S A requested security changes on Android, with the assumption that is in benefit to all phone users. But in fact they are tampering with my patient. You see many of this security upgrades are preventing me to use the FULL capabilities of my device. In fact do you know that with a few press button THEY! can block your phone, copy and even erase your phone!! If that gets compromise you do not think it is a Risk!

Now you said and I can read in Phone status windows that SELinux is disable. But that for me is all BullS****. I know, I may be wrong. I us the term SELinux to group all the security projects like knox and others. And that is a wrong assumption I do.

But I was in hope that when you said SELinux disable I could have the new stuff with my FULL use of android. Up to now I found it is just a fake. You may have disable SELinux on Kernel but Java still enforcing it. For example, many programs still can not access the external SDCARD and share the data with others apk. I have not try but the I guest I can not mount my wifi Hard Drive where I have my music, videos etc. And I know this is just the beginning. I will do some more test but but I bet you I will end going back to 4.2.2.

What I just said has nothing about your nice port to P5210, it is regards Android 5.1.

Returning to your port As I said, camera is not an Issue to me, but I will download and test it too. Sound... That is another issue, I like to have music and Movies on my device, I even use the alarms and other related stuff. I even has installed on my GT-P5210 WIFI an application to have phone calls via WiFI and phone messages. I had a NewYork phone number where I could received calls. I did not used that much because the FREE carrier I found did not allow me to make calls to Puerto Rico locals and cells, but it allowed me to send messages witch was just nice. So without audio I can not receive calls!

Any way keep the good work.
[Galaxy Tab 3 General] r2d23cpo:
Oh I forgot?

I see you post 3 new files.

Whats different in this:

houdini-5.0-20150415.zip

playstore-x86-5.1-20150415.zip

versus the old *-20150411.zip files?

I understand that CM12 recovery may have no value due to it not working. That is fine. But when I explode Recovery image It do have a different ramdiskfs that it is of interest to study and compare.

The initrams or ramdiskfs are important to me because I am finding a way to run Ubuntu natively. I know it has no meaningful to CM12/AOSP other than it allow to boot.
[Galaxy Tab 3 General] nels83:
Sort of, you can take pictures and scan QR Codes at least. I didn't try anything else.

Thank you. It's a lot of copy/paste in fact... Most of the work comes from others (thank you all Android devs by the way :good:)

I don't see what you mean. Every app having SDCARD permissions can read and write on the SDCARD. As for your wifi HD, how do you want to access it ? I have one at home and play music and videos without problem (using UPNP or SMB or FTP).

So do I. That's why I started working on it but it seems to be more complicated that I thought...

Wow, you're fast ;). I started the upload before going to work so it will be available when I return. Anyway, these are the versions I talked about earlier : they have addon.d scripts so you just have to flash these 2 zip files once. You will be able to dirty-flash next builds of cm-12.1 without flashing them again.

No problem, you can find it in the Extras folder on androidfilehost.

That's strange. The only thing I forgot is to enable mtp by default but after I enabled it in the Android Settings everything worked fine. Next build (tomorrow or the day after I think) will have it enabled by default, I'd be interested to know if it works oob for you.

Edit:

I have this problem sometimes : MTP doesn't work when I boot the device with USB plugged in. I have to remove and reinsert USB to make it work. Maybe it's related.
[Galaxy Tab 3 General] r2d23cpo:
Yes i did also quick test and seems working. Now, I may not understand 5.1. I do not see the Camera Icon in any place. Only when I press Power then I see the camera ant the right down corner. I bet you Icon is hiden in some place else like all new thing does. I do hate new things. jijiji

This feeling is NORMAL. In any work we always have to thank some body else initial work. None of us got to this world with all the knowledge required to do anything. Here is where the forum rules are not fair. Anytime some body can come and complains that we base our work in his. That is a fact to all of us. The issue get strongest when the programers request a coffee or a beer!

Partially true! Many developers had update their app to go around SDCARD limitation. So depending if you app has been updated you may see or not this issue. If you use all apps to test then you encounter the no access to sdcard! I know, now you may say it is my fault for using all apps. we will see it in the future.

"how do you want to access it ?" I will love to mount my external wifi HD as a folder in lets say "/storage/SMB" or we could name it "/storage/CIFS". The any app can access the external files. This method used to work in Android versions before 4.2.2. For 4.2.2 it requires some manipulations.

There are more issues like we can not change permit to files in SDCARD area. Try to change permit access to 777 in a file in SDCARD. You can't.

So how I do it, we are forced to used app that implements their own CISF/SMB protocols. I use ES Explorer. But in the past I used to used CIFS Manager witch no longer works for the reasons I exposed. You see our beloved N S A has forced Google to implement a new security strategy. This strategy request and leave tracking information any time you access files, read, store or execute. Clearly the intention is to track users file movement. They even try to force SDCARD useless in favor of their own supply clowds. This new security protocol is incompatible with the old. Or so they claim.

Now I ask you what do you use that you claim have no problem mounting CISF/SMB external folders?

No I am not fast it just happens that I saw you post at the same time. Just luck.

Yes I can confirm that I install new CM12 over old without lossing any file. I only clear Dalvick Cache.

Now please explain me how is that you " enable mtp". "after I enabled it in the Android Settings everything worked fine." Where is this setting that I can not find. That may be the reason, it does not matters how I change it in kernel, dalvik java is changing it back to whatever setting you are referring too.

..[/QUOTE]

No I try that it did not work for me.
[Galaxy Tab 3 General] nels83:
It seems to happen when you have no camera on first boot (after a fresh install). The only solution I found is to wipe/factory reset (didn't have time to investigate).

Then it's a problem with the app, not the OS ?

Oh, I didn't say I mounted a CIFS folder, just said that I could access it. In fact I do just like you using ES Explorer. Regarding CIFSManager, I'm sure it's possible to make it work on 5.1 (but it will need some work).

I think both problems have to do with the new fuse system used in Android. Try changing permissions in the "real" mounted folder (/mnt/media_rw/sdcard1) and it will work (if your SDCARD is formated in ext4). However Android will still provide you "fake" permissions in /extSdcard (virtual folder).

You have to go to Settings/Storage. You then have a menu "USB computer connection" where you can check MTP/PTP/Charge only.
[Galaxy Tab 3 General] r2d23cpo:
Some times I think you have a different OS than I have. Jijijiji

I can not find that USB computer connection?
[Galaxy Tab 3 General] nels83:
It's in the main menu (I can't remember the name, the three dots in the upper right corner of the screen).

New version uploaded : cm-12.1-20150416-UNOFFICIAL-p5210.zip

- CM updated

- Auto brightness by default

- MTP by default ;)

I tested with a full wipe and my device showed up immediately after the first initialization (I'm on Debian Jessie).
[Galaxy Tab 3 General] r2d23cpo:
jijijijiji this is amazing. I made the s7up1ds of the questions and your answer got you all those thanks!!!!! I bet you many where lost as I did. In fact this proves many are behind your work reading, they are just some how lazy to post.

Any way I know the trouble now. We the owners of Android 4.2.2 are custom to use th [MENU] button. But it seems 5.1 remove the use of the Menu button in favor of the 3 dots at the top!!! WAO.
[Galaxy Tab 3 General] nels83:
Just uploaded cm-12.1-20150420-UNOFFICIAL-p5210.zip

New in this version:

- Fixed charger mode

- Vendor files extracted automatically from XXUBOB1 rom (I still maintain the vendor repo for those who need it)

- PowerHAL from android-ia (will need work on the kernel side to be fully functional)

- Use opensource libintelmetadatabuffer and libwsbm (from main repo)

- Device tree cleanup

Still no video encoding and no sound.

[MENTION=1649190]Angel_666[/MENTION] I saw you managed to define audio routes when using samsung's audiopolicy (should have read the entire thread before trying anything :D). Can you tell me how you did it ? I tried but never succeeded (even the stock audio.primary TinyUCM cannot define them, maybe it has something to do with parameter-framework which I didn't include)

[MENTION=6109572]xTear[/MENTION] Still working on the P5200 tree but I'm not really comfortable with all that ril stuff.
[Galaxy Tab 3 General] blits01:
when will cm12 for p5200?
[Galaxy Tab 3 General] Angel_666:
It seems that our device do not use parameter-framework like other Intel devices. Samsung wrote they own audio blobs for sound. To define audioroutes you need samsung's tinyalsa lib, samsung sound configs from /etc folder, samsung audio primary and policy libs and some blobs from /system folder (dependencies). Can't remember they all names for now, but you can see needed in logcat. After all libs are in-place we can see audiorouting starting in logcat, but then Mediaserver crashed. Or as another variant - we can take opensource audio for WM 1811 from CM but no sound playing by mediaservice - only by tinyplay and 48KHz only (no resampling).
[Galaxy Tab 3 General] nels83:
When it's ready ? I know it should be available from what I said but it does not boot yet (probably RIL problem). But don't worry, I'm working on it.

Oh god, thank you! The only file I didn't try whas tinyalsa.so... It seems the magic happens here.

Apparently Lollipop does a better job for resampling, I didn't have any problem using P5100 HAL as a base.

Expect something good soon ;)
[Galaxy Tab 3 General] nels83:
Uploaded cm-12.1-20150421-UNOFFICIAL-p5210.zip (sources are updated on github as usual)

New in this version:

- Audio! (basic for now, no bluetooth audio support)

Happy flashing ;)
[Galaxy Tab 3 General] blits01:
How to install? p5200? now installed stock 4.4.2

error with wipe system,data,dalvik.cache. Philz recovery. How to fix?
[Galaxy Tab 3 General] Angel_666:
For working RIL we need samsung ril files for xmm6262 https://github.com/kumajaya/android_hardware_samsung/tree/cm-11.0/ril

In my case - ril works fine with this sources. But it was on 4.4.4 dunno how it will be on 5.1.1
[Galaxy Tab 3 General] Dexter885:
Thank you so much for the nice porting!

I installed the last version, everything works except hangouts. I monitored hangouts and crashed with this message: 04-22 20: 12: 51 142: A / libc (19488): Fatal signal 11 (SIGSEGV), code 128, fault addr 0x0 in tid 19684 (ChromiumNet).

in my opinion it's something about libhoudini.

Thanks again "Bravo"!
[Galaxy Tab 3 General] nels83:
This is for p5210 only for the moment. I'll let you know when a p5200 will be ready.

Thanks, I'll take a look. I only tried with the stock ril at first.

I'll need more than that to investigate but I'll try to take care of hangouts directly if you give me some time ;)

Glad it works for you.

btw I found and fixed the problem in tinyalsa which means one proprietary blob removed.

I'll explain for those who might be interested: I traced ioctl of alsa at the kernel level and found out that SNDRV_CTL_IOCTL_ELEM_READ and SNDRV_CTL_IOCTL_ELEM_WRITE had different values when using samsung's libtinyalsa.so.

After looking through the sources I found that those values where calculated at compile time and using size of snd_ctl_elem_value as a parameter. Bingo! Size of the data member of snd_ctl_elem_value is 1024 in the kernel and 512 in bionic. So simply adding asound.h of the kernel to the device tree fixed it.
[Galaxy Tab 3 General] social-design-concepts:
I think there is actually a commit about this in one of the Intel sources
[Galaxy Tab 3 General] nels83:
I don't think it has something to do with this particular problem. I didn't touch tinyalsa (if I understood what you said).

It would be a nightmare to maintain tinyalsa if we had to take into account every possible kernel/alsa configuration.
[Galaxy Tab 3 General] social-design-concepts:
yeah i overlooked the in the device tree part of the explanation.

[MENTION=6587211]nels83[/MENTION] , this was the commit i was referring too : https://github.com/social-design-co...mmit/1ea57d6f13de7da0ee6ceb8a32d7133c1621efed
[Galaxy Tab 3 General] Angel_666:
Ok. Using Nels83 git as a base and make some changes to the p5200 init files (change santos10wifi to *3g - please fix :) ). One more fix for me is compiling problem of /framework/base, coz it differ in Nels git and actual CM git - fixed. P5200 image ready and device works fine (without ril yet). Tons of proprietary crap are finaly removed.

Big thanks to Nels83 for his clean, well-formed and cool sources! :)

View attachment 3277652
[Galaxy Tab 3 General] xTear:
What are the bugs for now?

Does Audio work on P5200?

Could you upload a build?
[Galaxy Tab 3 General] Angel_666:
Yes. Audio works fine, i think almost all works fine exept hw video decoding\encoding and ril.
[Galaxy Tab 3 General] xTear:
Sounds nice, did you check if the vibration works? except if you use the google keyboard and touch at a char
[Galaxy Tab 3 General] Angel_666:
Vibration works fine.
[Galaxy Tab 3 General] xTear:
Could you please upload your build? :/
[Galaxy Tab 3 General] Angel_666:
https://mega.co.nz/#!sRdU2aKB!YJrOhtjUGSVxNBL8605Vzt17cl8smI0MT-ttAgCcl6A Odin flash file. Contain boot and system image. For testing purposes - ril not working yet.
[Galaxy Tab 3 General] kb8no:
Please give me a clean link to these uploads. I just can't find them.
[Galaxy Tab 3 General] xTear:
MD5 Hash isnt correct, can' flash it with odin
[Galaxy Tab 3 General] Angel_666:
I am just download it from this link and flash - all ok, try to redownload file
[Galaxy Tab 3 General] xTear:
It was the filetype 'md5', i had to remove the .md5 so its only a tar file, and i could flash it
[Galaxy Tab 3 General] nels83:
Could you tell what were the needed changes ?

Good catch, should be fixed now ;) And I bet my device tree should boot now.

Oops, forgot to tell you that I now use CM's /frameworks/base since they fixed the bugs.

I started working CM's ril like you suggested, I'll let you know the progress.

And it's only the beginning ;)

Thanks. You put a lot of efforts into this, it was easier for me since I started working on LP (which needed very few patches).

Sure, it seems I can post links now :) : cm-12.1-20150421-UNOFFICIAL-p5210.zip
[Galaxy Tab 3 General] social-design-concepts:
[MENTION=6587211]nels83[/MENTION] can you post your local manifest