yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] juniorhxcx:
Daniel,

I can only thank you for all the work he is having to keep our equipment (62xx, 68xx, TXX) alive and really Kitkat will give a new breath, for even in an experimental state already see how the device works smoother. A feather can not help, but I'm looking forward to seeing this in functional status.

As a suggestion, I honestly do not know the procedures, but it would be interesting to ask an official support OmniROM (ROM promising, others liked) and CM. The Galaxy SII has the same hardware, in which the use OmniROM and this magnifies the ROM. Maybe they (Team OmniROM) may offer official support or at least help in these matters!

I'm almost begging for support OmniROM, and Entropy512 (http://xdaforums.com/member.php?u=591147&nocache=1&z=3487892739940434) Kindly reply me: "Someone who is working with one of Those devices and has it working needs to submit it. "

Sorry for my english
[Galaxy Tab 7.7 Android Development] 11nn93n9:
Hi Daniel,

Whe I try to repo sync, I was stopped by the error:

"fatal: Couldn't find remote ref refs/heads/cm-10.2"

"Cannot fetch danielhk/proprietary_vendor_samsung_smdk4210."

I was trying to build a cm-10.2 version.

I checked your repository and the folder was right there.

I am new to building android rom. There must be something obvious that I missed.

Thanks.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I think you get this line from my PAC manifest.

That was base on cm-10.1, default is cm-10.1. If you take a look of the project danielhk/proprietary_vendor_samsung_smdk4210 on github, you will find only one tree cm-10.1. cm-10.2 can use the same tree. I'll find time to update it later.

When you build cm-10.2, default tree is cm-10.2. The line without a revision will assume the default. That's why you can find it.

Your solution: Add the revision=cm-10.1 at the end of the project.

.... danielhk/proprietary_vendor_samsung_smdk4210" revision="cm-10.1" />

Good luck!
[Galaxy Tab 7.7 Android Development] 11nn93n9:
Thank you for your help. Working on it. Its a big learning curve for me.
[Galaxy Tab 7.7 Android Development] 11nn93n9:
I made up to now the most progress with Ubuntu 13.04 64bit version building the cm 10.1 version.

With Ubuntu 12.04 and 13.10, I have been stopped much earlier than on 13.04.

Now I encountered the error below when running build-k p6800:

target thumb C++: libstagefright <= frameworks/av/media/libstagefright/ACodec.cpp

frameworks/av/media/libstagefright/ACodec.cpp:53:24: fatal error: sec_format.h: No such file or directory

compilation terminated.

make: *** [/home/lgeng/android/rom/out/target/product/p6800/obj/SHARED_LIBRARIES/libstagefright_intermediates/ACodec.o] Error 1

make: *** Waiting for unfinished jobs....

I downloaded the folder that contains the sec_format.h file from https://android.googlesource.com/device/samsung/crespo/. But It is not clear to me where to place the folder.

Thanks.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Not much I can tell. You have to provide the manifest.xml and local_manifest.xml if exist. And device tree changes if exist.

1. build-k is for kernel building only. frameworks_av seems not relevant.

2. crespo is another device. Not the right way to get missing file there.

3. With proper settings and manifest, Ubuntu 12.04 to 13.10 (which I'm using) have no apparent different for building.

If you are building cm-10.1, it is mature. No way there is missing file.

With no other info., I guest there is something wrong with your manifest or device tree. Mixing version projects, wrong flags in device tree, etc.

You might need more reading on what is device tree and manifest first.

Good luck!
[Galaxy Tab 7.7 Android Development] tom411:
Hi,

can you help me with integrating device to manifest.xml? I think there's the problem because everything runs fine until I write luch cm_p6200-userdebug, becuase it shows me that the device isn't found and in /android/rom/device, there isn't any folder called /samsung/p6200. I did everything by the guide, I only changed the local_manifest device info to p6200, because I own it. I'm using Ubuntu 14.04. Thanks for your help.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Not much details. next time provide detail. At least, send me your local_manifest.xml. It is definitely the source of your problem. You haven't tell which cm you built too.

I don't know what's wrong because I can't see anything in your side.

But I can tell you that device tree of p6200 didn't download. Check the typings of your local_manifest.xml. It should match the one in github.

Good luck!

TO ANYONE, YOU HAVE TO PROVIDE DETAILS. OTHERWISE, I DON'T KNOW HOW TO HELP!

I really don't have time to guess. You have to forgive me if I ignor your post.

From Nexus 7 上的 Tapatalk
[Galaxy Tab 7.7 Android Development] tom411:
Okay, sorry for it, I didn't know you need it. I want to build a Cm-11. I looked at my local_manifest and I think it's correct. Here is it
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
edify question for our 815's

Taken from one of your script's

mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");

Installing a .txt into sdcard0/data through .zip in recovery.

I used linux command to find paths for each of the memblocks - but didnt know which path, partition, I am looking for here. /system /userdata etc UHHHH

so to mount to the "sdcard0 /data"directory to install a plain .txt file would be ???

mount("ext4", "EMMC", "??????????????", "/data");

also can I call "/data" anything - like "/datadog" - since this is just a reference to a mount point and is temporary?

One other quicky

First I found this in an edify tutorial -

"/system partition is automatically mounted. this command is needed when you need to mount another partition beside /system or in any condition when recovery mode failed to mount your system partition. the system's location is /dev/stl9, cache /dev/stl10, and data /dev/stl11 (all partition type commonly rfs, will be differ if you have custom kernel or rom)."

since this is a custom rom does /system still auto mount - meaning in ref to to your code above - was it unnecessary but probably good practice or because this is a custom rom there are changes that move the location for /system. I noticed that " the system's location is /dev/stl9, cache /dev/stl10, and data /dev/stl11" was not in the memblock paths??

Start my intro to kernels tomorrow - Oh boy

Off subject - I knew Brazil - tough break with the injury though. Next wins - Argentina and Costa(CoastBaby)!! Going to bed now 6:00 AM WHAT.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't know what's your objective.

Some points to note:

1. command in updater-script use the function defined in updater-binary. Which are not necessarily a Linux executable command. These commands only valid in the updater-script.

2. You can only mount to an existing directory (mount point) which has not been mounted before. The mount command in Linux is a shell command which is executed by /bin/bash.

3. /system is mount by init following the sequence in .rc files. In recovery, a program is running to provide the interface for I/O. It doesn't require /system partition.

4. No matter which rom (stock or custom), the content of /dev are defined in kernel. Partitions info. is read from the PIT (partition info. table). Kernel will initialize the device at boot accordingly. They are similar to a harddisk partition.

5. our tab has emulated int. sdcard. It is part of the /data, at /data/media.

Hope these might help
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
earlier question simplified

My problem is with the mount command in a zip file to be used on our Carbon ROM partitions.

My goal is to make 4 different .zip files that can be installed with the recovery software. Each zip places one (the same) simple.txt file into a different folder then the previous zip did.

After I install the 4 zips I should be able to use my file manager app to view the simple.txt in each of the following folders

/sdcard0/data so the ????????? in => mount("ext4", "EMMC", "????????????", "/NAMEOFMOUNT"); would be ==>

/sdcard0/Download so the ????????? in => mount("ext4", "EMMC", "????????????", "/NAMEOFMOUNT"); would be ==>

/Root/data so the ????????? in => mount("ext4", "EMMC", "????????????", "/NAMEOFMOUNT"); would be ==>

/Root/system so the ????????? in => mount("ext4", "EMMC", "????????????", "/NAMEOFMOUNT"); would be ==>

This should give me what i need to fill in what I am missing on understanding this.

Thanks - I hope that this understandable

Off subject - Argentina taken care of biz - Costa is dead to me - Next winners Argentina and Germany
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
Just about there

6GB with intel I5 -1TB- is now setup as a dual boot with Windows 8.1 and Ubuntu 14.4. All the packages are installed etc.

My linux flavor is ARCH or Manjaro (arch based) - Not a big fan of unity, but since I did not want any pitfalls for support reasons I will use Ubuntu for now.

I now have a descent grasp on GIT and repo, as well as installing cyanogen on one supported device. It would appear that to install on our device any of the custom roms I would just need to provide a local manifest with the proper projects.

I am a little fuzzy on a few things but I think if you could please post two (i815's) local manifest's for two of our newer kitkat roms say Omni & Slim I should be able to figure out my answers or at least narrow down my misunderstandings to exact questions.

Thanks

All Hail GERMANY - - that final game was a real snooze fest.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I'm going to see my mom for 2 days. I'll see if anything missing when return.
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
understanding the local manifest

So this part is to utilize bluetooth on our tabs...

{

<remote fetch="https://code.google.com/p/" name="gcode"/>

<remote fetch="git://git.kernel.org/pub/scm/bluetooth/" name="korg"/>

<remove-project name="android_external_bluetooth_bluedroid"/>

<project name="bluez" revision="master" group="pdk" path="external/bluetooth/bluez" remote="korg"/>

<project name="sbc" revision="master" group="pdk" path="external/bluetooth/sbc" remote="korg"/>

<project name="aosp-bluez.glib" revision="master" group="pdk" path="external/bluetooth/glib" remote="gcode"/>

<project name="aosp-bluez.device-lge-mako" revision="kitkat" group="device,mako" path="device/lge/mako" remote="gcode"/>

}

This fixes our wireless...

{

<remove-project name="android_external_wpa_supplicant_8"/>

<project name="danielhk/android_external_wpa_supplicant_8_ath" revision="cm-11.0" path="external/wpa_supplicant_8_ath" remote="github"

groups="pdk"/>

}

This supplies drivers for tab specific hardware - camera -video -sound etc...

{

<project name="android_hardware_samsung" revision="android-4.4" path="hardware/samsung" remote="omnirom"/>

}

This supplies modem info...

{

<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode"/></manifest>

}

do I have this correct?? YES/NO

If so, then I should now be able to sync with all three of these roms and build a nightly?? YES/NO

If I venture into a different 4.4 rom then it looks like the following line would be the real change (suited to their repository)

<project name="android_hardware_samsung" revision="android-4.4" path="hardware/samsung" remote="omnirom"/> ?YES/NO

Thanks -
[Galaxy Tab 7.7 Android Development] daniel_hk:
Almost, but service mode is unique to Samsung phones. i815 might have different app but I can't find it yet.

wpa update is mainly for hotspot. hardware legacy also need modification for hotspot to work.

Good luck!
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
help

typed in lunch command and got this

Lunch menu... pick a combo:

1. aosp_arm-eng	33. slim_jflte-userdebug

2. aosp_x86-eng	34. slim_ls980-userdebug

3. aosp_mips-eng	35. slim_m7-userdebug

4. vbox_x86-eng	36. slim_m7spr-userdebug

5. mini_x86-userdebug	37. slim_m7vzw-userdebug

6. mini_armv7a_neon-userdebug	38. slim_m8-userdebug

7. mini_mips-userdebug	39. slim_maguro-userdebug

8. slim_bacon-userdebug	40. slim_mako-userdebug

9. slim_crespo-userdebug	41. slim_manta-userdebug

10. slim_d2lte-userdebug	42. slim_moto_msm8960-userdebug

11. slim_d800-userdebug	43. slim_moto_msm8960dt-userdebug

12. slim_d801-userdebug	44. slim_n5100-userdebug

13. slim_d802-userdebug	45. slim_n5110-userdebug

14. slim_d803-userdebug	46. slim_n5120-userdebug

15. slim_deb-userdebug	47. slim_n7000-userdebug

16. slim_endeavoru-userdebug	48. slim_n7100-userdebug

17. slim_falcon-userdebug	49. slim_p3100-userdebug

18. slim_flo-userdebug	50. slim_p3110-userdebug

19. slim_galaxysmtd-userdebug	51. slim_p5100-userdebug

20. slim_gkatt-userdebug	52. slim_p5110-userdebug

21. slim_geeb-userdebug	53. slim_p700-userdebug

22. slim_geefhd_att_us-userdebug	54. slim_pyramid-userdebug

23. slim_grouper-userdebug	55. slim_skyrocket-userdebug

24. slim_hammerhead-userdebug	56. slim_t0lte-userdebug

25. slim_hlte-userdebug	57. slim_t0lteatt-userdebug

26. slim_honami-userdebug	58. slim_t0ltetmo-userdebug

27. slim_i777-userdebug	59. slim_tilapia-userdebug

28. slim_i9100-userdebug	60. slim_toro-userdebug

29. slim_i9100g-userdebug	61. slim_toroplus-userdebug

30. slim_i925-userdebug	62. slim_v500-userdebug

31. slim_i9300-userdebug	63. slim_vs980-userdebug

32. slim_i9500-userdebug

first guess local manifest did not sync??

Is our tab listed above and i am not seeing it??
[Galaxy Tab 7.7 Android Development] biopsin:
add to vendor/../vendorsetup.sh

add_lunch_combo slim_p6800-userdebug
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
how does recovery mode get enacted?

You press the power button for standard mode and the boot.IMG gets called.

You press power button and volume up together for recovery mode and the recovery.IMG gets called.

You press power button and vol down together for download mode. Uu hhhhh what gets called????
[Galaxy Tab 7.7 Android Development] daniel_hk:
download mode is similar to fastboot in the Nexus series. This is the built-in program (boot loader) of the CPU.

Each single chip micro processor has internal ROM which holds the startup program at power on. Most of them can only be accessed via JATG (Joint Test Action Group, IEEE 1149.1). There are contact points and/or socket in the PCB for JATG connection.
[Galaxy Tab 7.7 Android Development] biopsin:
ori to portrait (cm10)

Hey,

I´m trying to correct the default orientation on cm10 to portrait (recovery, boot, lockscreen) and the JB kernel source already have those of ICS rotations in mach-px.c - just wonder if I should continue flip the switches around in the mach-px until I find portrait, or is there yet another place this needs to be adjusted? Daniel you mentioned a fix in platform?

Would it help to backport this logic
[Galaxy Tab 7.7 Android Development] daniel_hk:
The default orientation is landscape since HC. The LCD parameters are the same in HC, ICS and JB kernel.

Later, I changed the telephony service default orientation to fix the phone call orientation.

The only affected is the boot animation so it is not require to change the kernel now.
[Galaxy Tab 7.7 Android Development] dcervi:
Hi Daniel,

Following this guide and using your device trees, how hard it will be to build a non customized, AOSP rom for our tablets? Do we have all needed drivers, or there will be more work involved to get it fully working?

I'd like to have a multilanguage kitkat rom as close to 'google stock' as possible, but I have only basic programming skills and never built a full android rom before. Do you think it's doable by a noob like me?

Or maybe you could do it, if it's not too much work. I think many people would be also interested...
[Galaxy Tab 7.7 Android Development] daniel_hk:
It is not difficult to build a rom but AOSP is for Nexus devices.

For our tab, there are quite a lot of work to prepare.

eg. AOSP doesn't support things like custom mkbootimg, and some Samsung specific flags. You have to modify the build/core/Makefile.

Add the breakfast/lunch entry and fix the errors during build.

Other roms might already included all or some modifications.

For every rom to work on our tab, we have to modify

1. framework_native to correct the color space.

2. framework_base for rotation glitches and lock screen orientation, etc.

3. Telephony service for call screen orientation.

4. and a few hardware related things.

AOSP don't have the custom features like Quick settings' modification, advance boot menu, Power menu items(no screen capture), etc.

For myself, I don't think I can adapt after spoiling by the custom features. I don't think anyone flashing custom roms would too.

I have tried building AOSP l-preview for a few days. I just tested it for a few minutes after It's out. It is not suitable for me without modifications.

PA is something like that now. I have upload a patch but their reply was "Nexus devices don't need it". I have to drop it after tried for a few times...

You might think closer to AOSP would be more stable. I think so too but there are necessary modifications and blobs required to make our tab work. Since Samsung won't deliver any update for our tab anymore. With the existing outdated blobs, we can't expect much....

I hope that answer your question.
[Galaxy Tab 7.7 Android Development] dcervi:
Ok, so out of my scoop, for the moment. I'll try to find a rom with smooth screen scrolling trying the ones you've already built, then.

Thanks and kind regards!!!

David.
[Galaxy Tab 7.7 Android Development] pinsb:
Building modified stock......

Daniel

Your work on this has been much appreciated and I'm looking at doing my own build of the last stock that was released....DXMD3

Specifically what I'm looking at updating are some of the Google Apps with later versions, including some apps I want, a changed boot audio and by far the most important the fix for 5Ghz wifi which got broken on that build. While much of the stuff in the later builds is great to be honest I need stability over features and in my environ (Central London) the ridiculous number of WiFi lans is a major PITA, however 5Ghz is almost clear.

So if I could get a working build as per above I'd be very happy, if you could let me know what ended up being the 5Ghz fix I'd be grateful.

Regards

Pinson
[Galaxy Tab 7.7 Android Development] daniel_hk:
Hi Pinson,

My friends always say that no one can live in London. You must be some kind of Highness.:D

I'm sorry to say that you can't build a stock rom. The source Samsung released only contain the kernel. Which is only to fulfil the Open source regulation of Linux kernel.

The only thing you can do is rebuilding the kernel.

For gapps, you can update/add them in Play. The one in the rom will be disabled.

For wifi, it is mostly the platform issue. 4.1.2 is not stable for 5GHz. You may try rebuilding the kernel with my driver.

Good luck,

Daniel
[Galaxy Tab 7.7 Android Development] pinsb:
Thanks for that, just out of interest have you tried your kernel with a stock 4.1.2 build and did 5ghz work?

Regards
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
building a rom for 7.7

Building CM11.

SO i have my build environment set up correctly - I think - followed step by step instructions from several sites and even used a preconfigured setup in VBox - Ubuntu 14 and a lubuntu variety. -All set up are on VB!!

Here is my local_manifest.xml with no concern for Bluetooth ability

<
?xml version="1.0" encoding="UTF-8"?>
-<manifest>
<remove-project name="CyanogenMod/android_external_wpa_supplicant_8"/>
<project name="danielhk/android_external_wpa_supplicant_8_ath" path="external/wpa_supplicant_8"/>
<project name="ohanar/android_hardware_atheros_wlan" path="hardware/atheros/wlan" revision="cm-10.1" remote="github"/>
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode"/>
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung"/>
<project name="danielhk/proprietary_vendor_samsung_smdk4210" path="vendor/samsung"/>
<project name="danielhk/android_device_samsung_i815" path="device/samsung/i815"/>
<project name="danielhk/android_device_samsung_smdk4210-tab" path="device/samsung/smdk4210-tab"/>
<project name="danielhk/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210"/>
</manifest>

Repo syncs great!

using Daniels zip to insert the required terminal.apk - the process goes on and on for a while - I start getting excited that I am about to compile my first rom

Then I get an error 1 in the area of RIL and the build halts.

Now I am not sure if this build or local_manifest is the problem or not? But if the LM and the build env are good then should not any person trying to build the rom get to the same error and stop? If another can build with the same LM why would I get stopped with an error and they do not???? Perplexed ?????
[Galaxy Tab 7.7 Android Development] scoobydu:
[MENTION=4948627]daniel_hk[/MENTION], is your local_manifest.xml the same for building CM12 as previous?

Thanks in advance
[Galaxy Tab 7.7 Android Development] daniel_hk:
Some project didn't have the cm-12 tree but yes now. The local_manifest is the same.
[Galaxy Tab 7.7 Android Development] scoobydu:
Ok, I understand it doesn't have its own tree as it unsupported and even supported devices don't yet have trees, but I assumed the local_manifest was the file to pull in your source from other locations to build the standard CM12 tree for the 6800?

Or have I missed something?

Cheers
[Galaxy Tab 7.7 Android Development] p3dboard:
Lt.col.johncross - Did you ever get your build environment going? Looking at setting one up myself, for my p6810 tablet