yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 7.0 Android Development] zach61797:
Unjustifieds panel fix works to bring back the animation. I don't k ow how or I would send the stuff. because i also have another weird thing where my offline battery pops up when plugged in but it only stays for like 5 seconds then dissapears it doesnt load or anything it boots up after that and no touchscreen
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
getting logs is quite easy, actually ;)

just run the following commands and you're good:

adb shell

su

dmesg > /sdcard/kmsg.txt

then you can upload the .txt file ;)

anyway, mind me PM'ing you a new test build, as I think I know how to fix it ;)

EDIT: About the offline charging issue, this sounds more like a ramdisk issue rather than a kernel issue. [MENTION=3034891]gr8nole[/MENTION], did you use the T211 offline charging binary inside the ramdisk?
[Galaxy Tab 3 7.0 Android Development] zach61797:
OK and okay with me
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Actually, the stock T211 boot.img does not use a charging binary. The new lpm mode they are using is causing the problems.

There is currently a charging binary in my ramdisk, but it isn't being used. The stock lpm.rc and init.charging.rc both have a lot of old code that Samsung left in that refers to services that don't even exist in kitkat. It's a mess.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
This is exactly why I start disliking Sammy every day I am working on this device a bit more...

Best example would be also wifi, some crazy binaries are starting services that are usually being started via init. This is also one of the reasons why I didn't push my wifi changes to github, simply because my workarouns are sometimes scripts being run via init, which are then starting the actual binary and also setting a property so the next script can be started via init, just to "emulate" the stuff those binaries would be doing on stock...

Let's just lable offline charging as not working for now, until we've been digging a bit deeper into the KK ramdisk

Anyway, I just got the confirmation from [MENTION=5492269]zach61797[/MENTION] that the bootanimation bug is resolved in the attached build. Sources are pushed to github as usual ;)
[Galaxy Tab 3 7.0 Android Development] SOHKis:
if you aren't comfortable using adb commands to create/pull logs, grab 'syslog' from the market - https://play.google.com/store/apps/details?id=com.tortel.syslog

create the problem you wish to log/report, and then open the application, select which logs you want to grab & then it will zip them up for you on the sdcard as well as give you an option to send them via email or any other application that supports sending zips.
[Galaxy Tab 3 7.0 Android Development] gr9nole:
Nameless rom wifi working?

SM-T210 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Tab 3 7.0 Android Development] bmatney:
Why don't you flash it and find out?
[Galaxy Tab 3 7.0 Android Development] safariking:
No this is mentioned over 100 times learn to read please
[Galaxy Tab 3 7.0 Android Development] DevMyAndroid:
We Need Your Help!!

Ok, many of you guys dont know, one of the devs for this rom messed up his tab while modifying his bootloader to get offline charging to work, this kind of brick is un fixable!! In order for him to continue this rom and the other projects he does, he needs a new Tab. lets donate some money to [MENTION=3034891]gr8nole[/MENTION]*so we can get him another tab! He is the best dev for our device. ★★★★BIG THANKS TO [MENTION=4246643]Tomsgt[/MENTION], he donated $50.00 dollars to help get gr8nole a new tab!★★★★ If you can donate, please donate anything you can to him. His paypal is*gr8nole@gmail.com
[Galaxy Tab 3 7.0 Android Development] DevMyAndroid:
[MENTION=3034891]gr8nole[/MENTION], if you based this off the new t210 kitkat, i bet that would fix a ton of bugs and stuff. It would just not be cm 11 because its 4.4.2 not 4.4.4
[Galaxy Tab 3 7.0 Android Development] HerroYou:
4.4.2 is the same as 4.4.4 but with minor bug fixes
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Actually, I am just updating all blobs to the 4.4 ones :D

It's gonna take some time, but I'm looking forward to test them ;)
[Galaxy Tab 3 7.0 Android Development] fahadali2315:
Hoping to see some more development here :) Would be happy to help if needed .
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Alright, I've been playing around a bit, but I can't (at least not yet) get surfaceflinger working. There is an issue with the graphics driver, but I don't know what exactly's the problem... strace is no big help either..

So if you want to take a look at it for yourself, just let me know and I can give you my latest build ;)
[Galaxy Tab 3 7.0 Android Development] safariking:
Nvm
[Galaxy Tab 3 7.0 Android Development] fahadali2315:
Pm me the build and i would surely look into it ;)
[Galaxy Tab 3 7.0 Android Development] El Brillantinas:
Waiting for more results and supporting this project, thanks for developing!
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Not to be picky, but Minecraft doesn't work.
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
And in case you all are interested, ART seems to work flawlessly with the built in apps.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
EDIT: sorry, though I was in another thread... nevermind :o
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
I messed with this some today, didn't get anything working though. :thumbdown:
[Galaxy Tab 3 7.0 Android Development] InSaNeO1488:
Looking forward to seeing this rom become a everyday rom ☺
[Galaxy Tab 3 7.0 Android Development] DevMyAndroid:
I Think development for this rom is grinding to a halt. :(
[Galaxy Tab 3 7.0 Android Development] safariking:
I think you are right
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
I agree. :( Which is why I'm trying to work on it in my spare time.
[Galaxy Tab 3 7.0 Android Development] m101dream:
battery

The battery life on this Rom is amazing I'm getting 18 hours out of it with auto brightness and moderate use tottaly different from the Rockettab Rom which game no more then 7. I'm very impressed
[Galaxy Tab 3 7.0 Android Development] safariking:
This one is not even booting where are you talking about
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Dude, it does boot, i have tested it
[Galaxy Tab 3 7.0 Android Development] wait4me2burn:
of course battery life is amazing wifi isnt running, bluetooth, hw composer or a long list of battery draining features are not functioning or working......yet......
[Galaxy Tab 3 7.0 Android Development] m101dream:
My bad I'm refering to th Dragon. Rom V1.. Hold on is this another rom? Am I on wrong thread??
[Galaxy Tab 3 7.0 Android Development] DevMyAndroid:
Wait. If this rom dosnt boot, why did it boot for me?
[Galaxy Tab 3 7.0 Android Development] Teknodad1974:
Yeah it boots fine. Just no wifi or Bluetooth...
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
This is the CyanogenMod 11 Development thread...
[Galaxy Tab 3 7.0 Android Development] m101dream:
Now Im really intrigued a cyanogenmod rom for the tab 3 would be imppressive to say the least. The ported stock rom is great itself but CM is even greater. Hope everything goes well in getting this up n running . thanks to everyone who puts in hardwork, time and energy in making all roms thank u all
[Galaxy Tab 3 7.0 Android Development] gr8nole:
OK guys, I know it's been a while, but I have a little bit of good news.

I did finally manage to get the hwcomposer working (with correct colors).

Still haven't even looked at wifi again. Today was the first build I've compiled in a couple months, so don't get too excited. I don't have much time to spend on this at the moment, so please don't ask for an eta.

Just wanted to let you guys know that I haven't given up.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Well that's some great news! Can't wait to see the sources you used (or changes to them, to be more precise :D )

About wifi, I might have an idea for a workaround (I wasn't completly hibernating either ;) :p ), but I will need to look into your new build then, regarding blobs/changed code (You used the KK blobs, right?)

But I am short on time myself, lately, so well, when you have the time, it'd be great of you could push your sources (if you don't want to make it public yet, you can also use a private repo on bitbucket, as it's sometimes easier to track all changes online on github or bitbucket ;) )
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Haven't had a chance to switch to KK blobs yet. That's next on my list. I will update my github when I get a chance, but it probably won't be until next week.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Awesome! One step closer is better then nothing.
[Galaxy Tab 3 7.0 Android Development] gr8nole:
[MENTION=4716493]laufersteppenwolf[/MENTION] and others

I have updated the following github sources to reflect how I got HWComposer working.

https://github.com/gr8nole/android_frameworks_base

https://github.com/gr8nole/android_hardware_libhardware

https://github.com/gr8nole/android_frameworks_native

https://github.com/gr8nole/android_device_samsung_lt02wifi

These are up to date with the CM sources as of today.

You will notice that in the boardconfig, I commented out the wifi stuff to prevent errors while building.

My first attempt to use KK blobs was not successful. Will try again at some point in the future when I get more time.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Did you make sure to have the modules in /lib/modules as well as in /system/lib/modules? Some blobs need them to be in /lib/modules. The easiest way would be to simply add a symlink in /lib/modules that points to /system/lib/modules. This way we are compatible with all ROMs, no matter where the modules are actually placed in ;)
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I did...Had them in both places.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] jboyed1999:
[MENTION=3034891]gr8nole[/MENTION] have you tried the kernel from your 4.4.2 KK port or is the coding different than what CM11 uses? I apologize in advanced if someone has asked this question already. Thanks
[Galaxy Tab 3 7.0 Android Development] rogersb11:
That wouldn't work. Even if the source supported both sammy and aosp it would need a different ramdisk to boot from. I'm a little behind but kernel isn't the issue I believe. [MENTION=4716493]laufersteppenwolf[/MENTION] built a cm any kernel zip that I'm sure works. Merging new blobs with previous work with workarounds ( necessary workarounds of course) is tedious because you basically have to re-break what you've fixed and figure out the puzzle all over again. You can't imagine the time it takes. Even thinking it takes forever you're underestimating. Tedious tedious tedious nonsense that ends up blurring together when in the zone. [MENTION=3034891]gr8nole[/MENTION] will get it I'm sure. This is all scratch which is insanely difficult without even a template to go from. Wow that sure dragged on. Need any help for something specific let me know and I'll work on it in spare time. Fully functional rom and I'll build a kernel with OC, linaro, and some extras with stweaks to setup
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Once again, the same old clarification :D

kernel != boot.img

A kernel does not contain a ramdisk, only a boot image does. ---> kernel + ramdisk = boot.img. I can understand the confusion though, as most threads say "kernel" and ship a boot image, including a ramdisk. This, however, is just because the usual way to flash a new kernel is to flash a boot.img, which of course needs a ramdisk.

When compiling a ROM, however, you also compile the kernel as well, which is then being used to create the boot image. So yes, you can use the new KK kernel, however, as far as I can see, the new kernel also requires the new blobs (and vice versa). So as long as we are using the old blobs, we need to stay with the old kernel as well.

BTW, [MENTION=3034891]gr8nole[/MENTION] where did the boot stop? I suppose it was a graphics issue, right?
[Galaxy Tab 3 7.0 Android Development] rogersb11:
Oh I know that. I build for a couple devices. Didn't mean to imply the boot.img was the kernel at all. Mainly was saying that a sammy ramdisk isn't going to boot cm
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Yes, surfaceflinger/egl errors.

10-17 12:13:11.722 I/SurfaceFlinger( 121): extensions: GL_EXT_debug_marker GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_EGL_image GL_OES_depth24 GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_rgb8_rgba8 GL_OES_stencil1 GL_OES_stencil4 GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_depth_texture GL_OES_packed_depth_stencil GL_OES_standard_derivatives GL_OES_get_program_binary GL_EXT_texture_format_BGRA8888 GL_IMG_read_format GL_EXT_blend_minmax GL_EXT_read_format_bgra GL_EXT_multi_draw_arrays GL_APPLE_texture_format_BGRA8888 GL_APPLE_texture_max_level GL_ARM_rgba8 GL_EXT_frag_depth GL_VIV_shader_binary GL_VIV_direct_texture GL_OES_EGL_image_external GL_EXT_discard_framebuffer GL_EXT_multisampled_render_to_texture GL_VIV_clamp_to_border GL_MRVL_texture_video GL_EXT_unpack_subimage GL_OES_element_index_uint GL_OES_mapbuffer GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc

10-17 12:13:11.722 I/SurfaceFlinger( 121): GL_MAX_TEXTURE_SIZE = 8192

10-17 12:13:11.722 I/SurfaceFlinger( 121): GL_MAX_VIEWPORT_DIMS = 8192

10-17 12:13:11.722 E/ ( 121): Window has been abandoned! return value -22

10-17 12:13:11.722 E/libEGL ( 121): eglQuerySurface:599 error 300d (EGL_BAD_SURFACE)

10-17 12:13:11.722 E/libEGL ( 121): eglQuerySurface:599 error 300d (EGL_BAD_SURFACE)

10-17 12:13:11.722 E/libEGL ( 121): call to OpenGL ES API with no current context (logged once per thread)

10-17 12:13:11.742 D/SurfaceFlinger( 121): Screen acquired, type=0 flinger=0x41bec450

10-17 12:13:11.762 E/libEGL ( 121): eglSwapBuffers:1060 error 300d (EGL_BAD_SURFACE)

10-17 12:13:11.762 F/SurfaceFlinger( 121): eglSwapBuffers(0x1, 0x0) failed with 0x0000300d

10-17 12:13:11.762 F/libc ( 121): Fatal signal 6 (SIGABRT) at 0x00000079 (code=-6), thread 121 (surfaceflinger)

10-17 12:13:11.812 I/marvellWirelessDaemon( 128): succeed to create socket and listen.

10-17 12:13:11.862 I/DEBUG ( 119): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

10-17 12:13:11.862 I/DEBUG ( 119): Build fingerprint: 'Samsung/cm_lt02wifi/lt02wifi:4.4.4/KTU84Q/30a541c07e:userdebug/test-keys'
[Galaxy Tab 3 7.0 Android Development] gecko702:
i fell in love with this ROM i love it but it kinda lags on me but still it shows how much effort you put into it ^^ looking forward for a stable release also the TWRP is fixed i kinda struggled with the old version but as soon as i tried flashing the ROM it lacked md5 checksum but still installed so i dont know if it will bring any future issues
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Which kernel were you using for the build with the working hw composer?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
4.2.2 kernel sources https://github.com/gr8nole/android_kernel_samsung_lt02/tree/4.2.2
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Are you sure you've pushed all your changes to github? Because it still isn't working for me:

http://pastie.org/private/qdvpr4wgel0rudy52eyskg#

EDIT: Actually, I'm getting the same log on stock KK :eek: What the hell is going on here?!?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I do believe I have included all updates that I made. The last couple builds I ran were on a new box that used my git sources. Are you using my vendor blobs (they are from the T110 4.2.2)?
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
yeah, I am using your blobs...

Would you mind PM'ing me your build so I can look into it?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
http://d-h.st/lZG
[Galaxy Tab 3 7.0 Android Development] snakeboy1011:
Can i ask, are we actually ever going to get cyanogenmod for this tab?
[Galaxy Tab 3 7.0 Android Development] bmatney:
Sure we will. You can either be patient like the rest of us, or you can make a working build yourself.
[Galaxy Tab 3 7.0 Android Development] iamcray:
Am I the only one not being able to install CM11 at all? I just install it from philz and reboot system and it just goes back to recovery. Help? Been trying everything here.[
[Galaxy Tab 3 7.0 Android Development] DuceTheTruth:
Read the thread dude...
[Galaxy Tab 3 7.0 Android Development] bangdes:
You should reflash the latest one, I have same problem when using old recovery. Try TWRP or CWM by gr8nole. He just updated the recovery on 28th Oct...
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Any chance a version with the working hwcomposer will be uploaded soon?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Look about 7 posts up.

Sent from my SM-N900V
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Accidently overlooked that...thanks.
[Galaxy Tab 3 7.0 Android Development] aaronjasper49:
are the devs still here?

im tired of waiting xD
[Galaxy Tab 3 7.0 Android Development] bmatney:
Then make it yourself. The people that have the know how are already working on it.
[Galaxy Tab 3 7.0 Android Development] inouext:
If you want a custom rom, you choose the wrong tab model. :(
[Galaxy Tab 3 7.0 Android Development] bangdes:
Perhaps it should be works if we tried to port cm10 (4.1.2) cause suitable with stock rom and system not too complicated as cm11
[Galaxy Tab 3 7.0 Android Development] aaronjasper49:
i didnt chose my tab my mom did :p
[Galaxy Tab 3 7.0 Android Development] gr9nole:
I hate cm tab3 7

Mustafa's Tab:D cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Tab 3 7.0 Android Development] svicenty:
But it's cm
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Perhaps. Kitkat is better though.
[Galaxy Tab 3 7.0 Android Development] bangdes:
I'd like to give some help, but repo sync the github it's very difficult to reach 100%. Any some idea?
[Galaxy Tab 3 7.0 Android Development] safariking:
you are never happy with anything we do for this community!
[Galaxy Tab 3 7.0 Android Development] steffano:
Is any one still working on this build it would be great to see cm11 on this tab it haves much more life to give:) maybe for some it wasn't the best tab but I think if the deve keep on they man get this a good stable build:D
[Galaxy Tab 3 7.0 Android Development] troy5890:
Hey guys I have a question would this rom work with the samsung galaxy tab 4 7.0 if I port it with permission from the creator. Also how did cm11 or any custom rom get on the tab 3 if it has a Marvell processor?
[Galaxy Tab 3 7.0 Android Development] Andromeda 90:
No.:D
[Galaxy Tab 3 7.0 Android Development] troy5890:
What do you mean by that
[Galaxy Tab 3 7.0 Android Development] hoang81:
gr8nole,

I saw that you push the HWComposer fix to your github. I would like to help with my very limited experience with development. I will download the ROM in a few minutes and test it out, and am syncing the repo right now. Please let me know if this project is still ongoing...
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I haven't looked at it in a while. I've pretty much reached the extent of ability (and caring).

Sent from my SM-N900V
[Galaxy Tab 3 7.0 Android Development] hoang81:
Well, thanks for your work so far on it. May I pick this up? If you don't mind, may I shoot some questions your way when I run into trouble?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I added you as a contributor, so you can update OP if you have any luck. :good:
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
I don't have much time lately, and in my rare free time I am working on cm12 for my phone, but feel free to ping me in as well if you've got some problems ;)
[Galaxy Tab 3 7.0 Android Development] hoang81:
Thanks. I synced the source last night and planning to pull the vendor and device tree when I get home.
[Galaxy Tab 3 7.0 Android Development] bangdes:
I tried to $ cat /proc/mtd .... nothing happened here

Or maybe there's another method to do this?
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
What are you trying to do? This device doesn't have mtd partitions
[Galaxy Tab 3 7.0 Android Development] bangdes:
That's the problem... except we have another method to pull boot.img directly. Do u have it? :p
[Galaxy Tab 3 7.0 Android Development] Unjustified Dev:
From adb shell

dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
[Galaxy Tab 3 7.0 Android Development] bangdes:
i just tried... and...

/dev/block/mmcblk0p9: cannot open for read: Permission denied

do I miss something?

*edit

Aha! I did it!

root@android:/ # dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img

24576+0 records in

24576+0 records out

12582912 bytes transferred in 2.855 secs (4407324 bytes/sec)
[Galaxy Tab 3 7.0 Android Development] iknight8:
Any major bugs still remain? Also does this support apps2sd? I have the T210R does this work on it? Thanks.
[Galaxy Tab 3 7.0 Android Development] Lincoln99:
Yes, major bugs still remain (such as no WiFi, Bluetooth, and the UI is still a bit laugh, even with HWComposer) Apps2sd I am not sure about. And it will work on the T210R.
[Galaxy Tab 3 7.0 Android Development] iknight8:
Thank you for the response. mine is a WiFi tablet and bug with WiFi defeats the purpose of the ROM :/

I will keep looking.
[Galaxy Tab 3 7.0 Android Development] hoang81:
Finally had some time last night to work on this. Got my sources up and running, built and booted successfully. I merged in the HWComposer fix, and now working on the WiFi.

On my latest build, I noticed a few configuration files for wpa_supplicant and p2p missing. However, I don't think this is the issue. The build is not recognizing the kernel module... somthing is not working correctly with the sd8xxx.ko that makes the build not see it alogether. I apologize for the silly question, and this is probably from my lack of experience building for this device... but where did this module source come from? Was this released from Samsung specifically for the LT02wifi? or were these pulled from elsewhere or another similar device? Pulling the stock ROM, I do not see the module within the build... I'm assuming that it is located in the ramdisk. I can pull it and split, but was hoping to not reinvent the wheel if I don't have to. Any thoughts?

Thanks.
[Galaxy Tab 3 7.0 Android Development] gr8nole:
In KitKat, the modules are in the ramdisk. [MENTION=4716493]laufersteppenwolf[/MENTION] was working on wifi, so he will be much more help than me for it.
[Galaxy Tab 3 7.0 Android Development] laufersteppenwolf:
Yes, I was working on wifi before, and I also got the modules loaded at boot, but with some dirty hacks. the main issue isn't wpa_supplicant or p2p, the main issue is still inside the ramdisk, starting the services at the right time in the right order. I was working on finding the right order using those mentioned hacks, so I can then later change the ramdisk (init) accordingly. IIRC, I also replaced some blobs with stock 4.1 ones, as the blobs used are from 4.2.2, in which the modules are already inside the ramdisk IIRC ( /lib/modules/....).

You can work around that by symlinking /system/lib to /lib, so both, old and new blobs are able to open the same module.

And about the module's origin, yes, it is an original Sammy module, built from sammy sources. BUT, the name has changed: sd8xxx.ko is the same as sd8787.ko. So make sure all your blobs are referring to the right modules (same is for the mbt module). You can check that by examining the binary with an hex editor and searching for the module's names (it's then either gonna be /system/lib/modules.... or /lib/modules/...)

If you've got a bitbucket account, give me the link of your profile and I can give you access to my private device tree and blobs repos (both of you, of course ;) ) But first up, it's a mess.... it really is :D I sometimes replaced some services with a script, which then opens the actual service while also triggering the next service to start... not really nice :D