yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] DE52:
No problem, at least it was a simple solution :D
[Galaxy Tab 10.1 Android Development] mroneeyedboh:
For some reason Im getting gapps force closing... It worked at first. Any idea?

cleared data and cache under app and its working.. Thanks anyway.
[Galaxy Tab 10.1 Android Development] palmwangja:
external memory 0MB?

Not sure if this is FAQ, but let me ask this symptom...

I flashed this rom on Google I/O edition of P4WIFI, but all external memory is just gone leaving only 0MB.

Even TWRP says it is 0MB, and no way to flash another ROM as no room for any activity...

:cyclops:

What should I do for this situation?
[Galaxy Tab 10.1 Android Development] Vlad_z:
http://xdaforums.com/showpost.php?p=56529341&postcount=359
[Galaxy Tab 10.1 Android Development] 1stHTCphone:
I was playing with multi screen. Now everytime I launch Chrome, it is on floating mode. I tried reboot; clearing app cache; diabling app circle. I still can't get chrome to launch normally in full screen. Any advise? Thanks in advance!

Eric
[Galaxy Tab 10.1 Android Development] palmwangja:
Thank you for the information, but then what could be the next step for me, who lost internal/external memory both in system and twrp ?

Unfortunately I don't have any nandroid backup.
[Galaxy Tab 10.1 Android Development] vaikz:
Flash stock rom via Odin.

Then do all the steps in rooting and flashing recovery thru Odin again.

If everything is working, then flash the latest twrp and then your referred ROM.
[Galaxy Tab 10.1 Android Development] iopxiang:
I think the newest chrome is incompatible with this rom. I have come back to version 38.
[Galaxy Tab 10.1 Android Development] Zefiroth:
Excellent ROM,best i've tried so far.

Small problem:Chrome stays in floating mode no matter what I do.(uninstall-reinstall chrome,clear cache,enable-disable window mode).Any advice?

Thanx in advance.
[Galaxy Tab 10.1 Android Development] jaibar:
I got this problem on another device and it annoyed me quite a bit. A quick Google search shows that this problem exists in multiple devices. and/or roms.
[Galaxy Tab 10.1 Android Development] AAccount:
Somebody on the omni team got netflix working on the tegra2 asus transformer. I activated the BoardConfigCommon flag they created for this fix. I'm not sure if it works for us though since I have no netflix. However there are **other** streaming websites to watch TV and movies :cyclops:
[Galaxy Tab 10.1 Android Development] thelazy8:
Can confirm Netflix is working on 6/9 build for WiFi.
[Galaxy Tab 10.1 Android Development] AAccount:
Forgot to mention that new builds are up. They use the cache partition for the dalvik cache. It's a really simple 2 line boot script ?

Sent from my GT-P7510
[Galaxy Tab 10.1 Android Development] ajabhi95:
Thanks for the awesome ROM man :good: Everything works like a charm although there is a minor bug that I've encountered. Random colors keep scattering over the video that is being recorded.
[Galaxy Tab 10.1 Android Development] XTeK2:
Cool rom for our old tablet.

AAccount tried to format the system under F2FS?

Thanks to the work.;)
[Galaxy Tab 10.1 Android Development] AAccount:
There's no more room in the recovery image for an f2fs kernel module. There's not even enough place in the recovery to enable kernel modules at all. The recovery kernel is so stripped down to the bear essentials ?

Sent from my GT-P7510
[Galaxy Tab 10.1 Android Development] thra1982:
Thumbs for for this ROM. Just installed it, and everything is running nice and smooth (as smooth as this old tablet can be ?) ?

Sendt fra min GT-P7500 med Tapatalk
[Galaxy Tab 10.1 Android Development] smartidoos:
wow , runs smooth and fast , trying out right now , rapport later thx brow:good::good::good::good::good:
[Galaxy Tab 10.1 Android Development] smartidoos:
Trying out Now, rom is great Thx mine old tablet Is Again a New one:good::good:
[Galaxy Tab 10.1 Android Development] tokomotxo:
A2DP not working :(
[Galaxy Tab 10.1 Android Development] AAccount:
I think that was a problem in Android 4.3 as well. I have no bluetooth speakers or headphones. I wanted to try and use my laptop as an overpriced bluetooth speaker but the people who are in charge of the Linux blueZ bluetooth software, in their infinite wisdom, apparently rewrote their stuff from v4.0 --> v5.0. Couple this with the fact that the Fedora team instantly jumped on the new version head first without thinking. This means all bluetooth programs are instantly broken because of the new version is not backwards compatible. So at this point, my laptop has just the "new" "better" bluetooth framework but nothing that uses it. I'm assuming the utilities will be updated eventually.

[Aside]

I actually prefer wired speakers/headphones because there of no sound compression and I don't have another thing to charge. (Not that I'll probably notice because I can't tell above 96kbps.) My main speakers are salvaged Altec Lansing speakers from a 1998 sound system. The internal electronics died so I wired the speakers manually to a 3.5mm plug. I guess it goes well with my salvaged 2004 era pentium 4 desktop which is my daily driver. Seriously, I paid $zero for the speakers or computer. It's maxed out for its time and with Linux it cold starts to the desktop in under 45seconds every time. (When I say starts to the desktop I mean I get my desktop complete with background and icons, AND the hard disk LED stops flashing.) That'll make me feel guilty to eventually replace it since some Windows laptops in BestBuy take over 45 seconds to boot (their hard disk LED keeps on going and going long after you hit the desktop). Obviously the ROM builds come from my laptop though...

[/Aside]
[Galaxy Tab 10.1 Android Development] jaibar:
[Q] [noob] not needed system apks?

I apologize for the noobish question, but I couldn't find if it has been asked before:

Are all those "phone" system apks really needed for a WiFi-only device? I mean, ROMs for this devide can include stuff like voice dialer, phone, mobile data, messaging/mms etc. etc. Is it safe to remove them altogether?
[Galaxy Tab 10.1 Android Development] Olivier V:
Yes, it is safe to remove them. I always do it and had no problems.
[Galaxy Tab 10.1 Android Development] ajabhi95:
I have run into an issue with Bluetooth sync with my car. When I connect my tab through Bluetooth to my car, music plays through the tablet speakers and not through the car speakers. Any suggestions on how to fix this?

Thanks in advance.
[Galaxy Tab 10.1 Android Development] dirtyreturn:
Hey [MENTION=2931572]AAccount[/MENTION] . Is there a way to use this rom on p4tmo?

If there isn't could you please explain where a place to start would be?

I built a little from source, that's about it.
[Galaxy Tab 10.1 Android Development] Lucas Kado:
Incredible ROM man. Totally awesome. Great job. It's really fast! Only KK & JB endemic bugs: bluetooth headset/speakers, WiFi direct, random colors in the upper side of HD video recording, few screen flickering, network activity not showing. Recently posted this on Nameless KK 4.4.3 thread.
[Galaxy Tab 10.1 Android Development] AAccount:
I'm not sure what the differences between the TMobile and international 3G tablets are. I did make CM10.2 TMobile builds when android 4.3 was "the thing". What kind of demand is there for the TMobile version at this point anyways? I may consider letting it run in the dead of night one day while I'm sleeping.

Ever since pershoot left some of the "meatier" bugs will be really hard to fix since I'm no expert. Together with kasper_h we got kitkat up and running with a lot of loosely guided trial and error involving mostly error. I appreciate the rave review but keep in mind that BeeGee and kasper_h also work hard on their roms. My personal opinion is that omni rom runs faster than CM and its derivatives. I think omni is a direct aosp derivative with their team adding in features they like. I ran CM11 and my omni version on my former I9000M and I felt that omni was more responsive. For the I9000m I didn't touch a single line of code. Of course I pulled in some of the best CM features like their amazing calculator and superuser. For whatever reason the omni team insists on using a proprietary supersu...???

Unfortunately I have no bluetooth accessories so I can't really look into the issue. I use the 3.5mm jack on my car with a long wire running into the passenger's leg area :p
[Galaxy Tab 10.1 Android Development] :
I flashed the new twrp in op, did a full wipe, and installed rom + gapps... but my internal sd doesn't mount so things force close like crazy. I tried a few times and with/without gapps, but same results. Any thoughts?

In the meantime, I went back to 4.2.2 and everything's fine..
[Galaxy Tab 10.1 Android Development] Lucas Kado:
I didn't ever pretend to scorn neither BeeGee's nor kasper_h's work. I know how demanding this is and I very appreciate everything you all developers do. English is not my mother tongue so maybe I wrote things I didn't want to mean... Please read it with caution.

You really made me an impression due to the responsiveness of this ROM, and it is something I've missing for so long that I thought it couldn't be like this, that our tablet was just too old. Anyway, it has never been as responsive as a phone of its age, even with much less HW potential on the paper, something I've never understand...
[Galaxy Tab 10.1 Android Development] AAccount:
I think the speed is from omni rom. I noticed a day and night difference on my I9000M. Not sure what the reason is for that device. I think part of the reason omni is faster on our tablet has something to do with omni's reworked screenshot implementation. I distinctly remember in CM10.1 and CM10.2 with the new 2 bar tablet ui if you switched it back to the 1 bar UI the responsiveness instantly went up. If you disable screenshot on CM10.2 with the 2 bar ui you get the responsiveness of the current omni rom. When kasper_h told me omni got screenshot working I was hesitant to enable it but he said this time it was different. I had to see it to believe it and to this day I'm still surprised. CM's and Omni's screenshot implementations are both compatibility hacks to work around the lack of sources for our tablet. I guess somehow Omni has a much more efficient work around. It also means Samsung/NVidia wrote sh***y drivers.

As another side effect of the screenshot workaround, I can finally use live wallpapers. I remember even back on stock honeycomb, every live wallpaper I tried caused the launcher UI to lag horribly.

But a big thank you for the positive review though :cyclops:
[Galaxy Tab 10.1 Android Development] .me:
Started getting orange wireless icon

Can't seem to get rid of it

Cleared hosts. Adjusted time made sure that time zone is correct. Did firmware reset and updated to latest firmware also

Flashed lollipop - all synced no problem

Any suggestions?
[Galaxy Tab 10.1 Android Development] DE52:
[MENTION=5451834]iopxiang[/MENTION] [MENTION=6161733]Zefiroth[/MENTION] [MENTION=3599815]jaibar[/MENTION] I've seen that a workaround, although a bit annoying is to go into recents after opening chrome and then clicking it. It should then open in full screen. If I find the solution I'll let you know but downgrading is probably easier if you haven't done so.
[Galaxy Tab 10.1 Android Development] 1stHTCphone:
The solution is on the post right above yours... LOL.. guess someone doesnt like to read..hehe
[Galaxy Tab 10.1 Android Development] AAccount:
Thanks to [MENTION=4404851]decatf[/MENTION] omni 5.0 is now alive. Say goodbye to this thread. Its successor will eventually be out.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Oh yes! I've waited for you to say this!
[Galaxy Tab 10.1 Android Development] jaibar:
Wow. Those are nice to hear news!

Old Tab is going to get L before official OTA for my nexus5 and 7 ?
[Galaxy Tab 10.1 Android Development] AAccount:
Omni Progress

Just an update on how things are going. There appear to be some very MAJOR QUIRKS in android 5.0. First of all, gapps doesn't appear to be properly saved when I flash each new nightly. Yes I do have the builds run @ 1am every night on my aging laptop. Now that shouldn't mean anything as you can always reflash gapps. However, this DOES cause a problem as the wifi service will always crash and cause a soft boot loop. As in, it will boot but keep going back to the boot animation every 5 seconds. The solution appears to be to flash the gapps and nightly together in twrp. I suspect this has to do with google's wifi location spy thingy I always opt out of.

Flashing nightlies is another issue. Fresh from my laptop they don't flash. update-binary needs to be swapped out to a kit kat one and the install script needs to slightly edited so that it isn't passing 5 arguments in for mount.

I got a nasty surprise last night that the stock email app doesn't work. It just crashes when you launch it. This is unacceptable to me because I HATE the gmail threaded email view. I managed to fix it by commenting out bad code. The new stock email app is actually very pretty once you it works. It's such a shame they shipped it all f***ed up.

Lastly, there are some random reboots that I have gotten the logcats for but don't appear easy to fix if I'm even good enough to do it. One of those random reboots was the gapps issue mentioned earlier. The other I've only caught once. However, omni seems to be doing a good job of keeping up to sync with google's many iterations of android-5.0 releases. (I started on r5. They're now on r7). Let's hope google gets their @$$ in gear in the lollipop code quality with each new iteration.

Check my github for all these changes. I haven't gotten to watch any anime since last Friday ?
[Galaxy Tab 10.1 Android Development] rtiangha:
I'm sure you've probably thought of this already, but make sure you disable your tweak of mounting whatever the ART equivalent of the dalvik directory is in /cache as it'll fill up quicker when the apps are recompiled on first boot. If you run out of space on /cache, you may encounter boot loops. That's what happened to me when I was playing around with ART on the Omni ROM.
[Galaxy Tab 10.1 Android Development] AAccount:
Surprise: in lollipop /data/dalvik-cache is now.... /data/dalvik-cache/{arch} where arch is the type of cpu like x86, arm, mips. Yeah I probably won't make the dalvik cache script part of this rom.

So I've finally figured out WHAT but now really HOW to solve the mysterious gapps boot loop. Turns out it wasn't gapps at all. It was just very coincidentally timed with gapps. If you don't have wifi turned on when the tablet boots it goes into a boot loop. You do get a 10 second ultimatum to "correct your mistake" though. You may turn it off after the boot but it MUST be on when you start it. I remember seeing decatf having a commit which automatically turns on wifi but didn't think it was necessary. Thanks to him, now I know how to make lollipop happy.

After suspecting it was the wifi, it took many iterations of rebooting with wifi on/off to confirm that it was the source of the problem.

However, the question remains why this is necessary. Oh, and another nasty surprise from this evening: the microphone is dead.
[Galaxy Tab 10.1 Android Development] JS_racer:
AAccount, thanks much for the update. much appreciate the time and effort.

loving your 4.4.4, brought new life back in my 10.1 wifi.
[Galaxy Tab 10.1 Android Development] decatf:
I noticed you didn't use the dlmalloc flag. Some apps were crashing without it. The new default is jemalloc but it appears to be problematic for our device. dlmalloc is the previous default.
[Galaxy Tab 10.1 Android Development] AAccount:
Oh wow, thanks for the inspection. I did attempt dlmalloc but got all kinds of weird compile messages. I think it was due to "stale leftover intermediates" and really really didn't want to site through 3 hours worth of compiling from scratch. I think I'll try and hunt down those intermediates.

Oh hey, did you manage to find out why the microphone isn't working. I purposely created a crash in places of the audio recording system to get a stack trace by doing.

int *pointer = (int*)1991;
*pointer = 2014;

What I've managed to find out is that in frameworks/av/media/libmedia/AudioSystem::getInputBufferSize(args...args) it never ends up calling AudioFlinger::getInputBufferSize and instead craps out. I put the crash code written above in the audioflinger function and android never crapped out, never gave a segfault in the logcat output. Do you really think this is because of the malloc?
[Galaxy Tab 10.1 Android Development] geocomp:
Thanks

I am really impressed that you and others are still supporting this tablet. I have been using your latest Omni build and love it. Can't wait for you to get all the bugs worked out of the Lollipop build so I can play with that version.:good:
[Galaxy Tab 10.1 Android Development] honhan0904:
I hope you release omni 5.0 soon

Thanks alot
[Galaxy Tab 10.1 Android Development] decatf:
I traced it to there too. I didn't have time to dig deeper but I tried computing the buffer size externally and it worked.

But this is a very ugly way to do it. Does not solve the real problem. Very ugly...

diff --git a/media/libmedia/AudioSystem.cpp b/media/libmedia/AudioSystem.cpp
index a50ea7d..c5ff82a 100644
--- a/media/libmedia/AudioSystem.cpp
+++ b/media/libmedia/AudioSystem.cpp
@@ -390,7 +390,12 @@ status_t AudioSystem::getInputBufferSize(uint32_t sampleRate, audio_format_t for
if (af == 0) {
return PERMISSION_DENIED;
}
- inBuffSize = af->getInputBufferSize(sampleRate, format, channelMask);
+ // inBuffSize = af->getInputBufferSize(sampleRate, format, channelMask);
+ inBuffSize = (1024 * sampleRate) / 44100;
+ inBuffSize = ((inBuffSize + 15) / 16) * 16;
+ inBuffSize = (inBuffSize * popcount(channelMask) *
+ audio_bytes_per_sample(format));
+
if (inBuffSize == 0) {
ALOGE("AudioSystem::getInputBufferSize failed sampleRate %d format %#x channelMask %x",
sampleRate, format, channelMask);
[Galaxy Tab 10.1 Android Development] AAccount:
YOU ARE A GEEEEEENIUS!!!!! Fake it to make it if you have to. It works in just about every industry on the planet. Surely it will work for us android hobbyists. It was on my mind to attempt faking the buffer calculation but I had no idea what the formula was. Where did you get that from?

I successfully taped myself whistling using a wave recorder app that apparently isn't on the market anymore. In addition to your patch I had to comment out these lines in frameworks/av/services/audiopolicy/AudioPolicyInterfaceImplLegacy.cpp in the function AudioPolicyService::getInput(crap load of args)

// already checked by client, but double-check in case the client wrapper is bypassed
/**if (inputSource >= AUDIO_SOURCE_CNT && inputSource != AUDIO_SOURCE_HOTWORD) {
return 0;
}

if ((inputSource == AUDIO_SOURCE_HOTWORD) && !captureHotwordAllowed()) {
return 0;
}*/

Yea, that's one more off the checklist of bugs.... I think???
[Galaxy Tab 10.1 Android Development] rahimskala:
Hi.Jumping charging indication from 9% to 2% once cured:confused:?Thank you.
[Galaxy Tab 10.1 Android Development] yoyosuper8:
Can't remove icons in home screen

Thank you all for your hard work to get this working. I was able to successfully install Omni 4.4.4 on my Samsung Galaxy 10.1 p4wifi tablet. Everything runs smoothly, no graphics glitches at all. The only problem I'm having is that I can't seem to be able to remove widgets or icons in the desktop or home screen. When I tap and hold on an icon/widget, I don't get the options I would normally get above the screen to either remove the icon, see app properties, etc. How can I remove icons on the home screen? This is the only thing that is bugging me a lot.

Any help is appreciated it.

Thank you

A
[Galaxy Tab 10.1 Android Development] vaikz:
Just drag the icon to the top middle of the screen and when the icon turns red then it will be deleted.
[Galaxy Tab 10.1 Android Development] AAccount:
Status Update

After using decatf's fix for getting the microphone buffer size, I rerouted any "hotword" detection to use the normal microphone source. I still would not recommend using hotword detection as it may leave the microphone on 24/7 and could be bad for battery life.

The stock camera app does not work. It crashes when switching front to back camera, it crashes when switching from photo to video. However, when on video it does record picture and sound. To be able to switch cameras on the fly, I'm using this camera app instead which has more options anyways.

I've used the tablet to play a 720p video on vlc while waiting for a class and it handled it without stutter, lag or any other problem. Of course, the file itself wasn't that big so that might be from lower bitrate.

I've previously mentioned fixing the crash in the stock email app and I've used it for 3/4?? days and it works perfectly. It looks just like the new gmail app except it's orangey-yellow instead of red. I also got a battery % to display next to the battery icon.

Lastly, I don't know if 3G is working on decatf's build but if it isn't working there it ISN'T going to work here. I'll have no way to diagnose it. Even with logcats, I'm not that good so the best I could do is look @ your sent in log cat, attempt some kinda fix (or put in crash code somewhere to force a stack trace), send you back the changed files, and wait for a result. Then the cycle repeats until the problem is fixed or my skills run out. To me, this painfully slow cycle is not something I wanna deal with.

Everything looks good I think... You can flash the build from twrp 2.8.0.0 but YOU MUST TURN ON WIFI BEFORE YOU REBOOT OR TURN OFF. Otherwise you will get about 10 seconds of usage followed by boot loops.
[Galaxy Tab 10.1 Android Development] jaibar:
I couldn't find link for p4wifi- it shows only kk builds.. Am I missing the link somewhere?
[Galaxy Tab 10.1 Android Development] AAccount:
Not yet... :p I want to run one more build with the latest omni sync.
[Galaxy Tab 10.1 Android Development] yoyosuper8:
thank you!

Wow... I feel so dumb right now. When I first dragged the icon to the top middle, I didn't wait long enough for it to turn red to remove it from the home page.

Anyways thank you for the help.

I do have one more issue, if it is one, that is the sound coming out of the tablet is now low than before. I've played several movies with this new rom using mx player with audio hardware decoding enabled and the sound coming out of the tablet is low. It is not as loud as before. Is there a way to increase the volume? The speakers on the tablet are fine. Before I flashed the new rom the tablet sounded great when playing music and videos. Any ideas? Thank you.
[Galaxy Tab 10.1 Android Development] decatf:
[MENTION=2931572]AAccount[/MENTION] are you getting the boot up when the charger is plugged in issue?
[Galaxy Tab 10.1 Android Development] AAccount:
Oh yeah, I am. Just discovered that. If I remember correctly, way back when I first started doing my kernel there's some kinda "lpm_charging_??something??" and "charging_mode_booting" thing in the kernel. Pershoot originally set charging_mode_booting somewhere and when I set that in the kernel it caused issues for people on stock rom. It's been ages since I've seen that.

I have to do some very annoying CS theory homework so I won't be able to look at it until late evening :(
[Galaxy Tab 10.1 Android Development] decatf:
As I understand it the playlpm program is the charger application itself. And yeah I went digging in the kernel there's a variable named charging_mode_from_boot. I tried setting it true before system shutdown but it appears to not do much other than toggle the touch screen off when booting into charger mode.

At this point I'm thinking the playlpm application might be crashing. Because the battery icon appears for a brief moment before the system does a full boot. That's if my understand of how it works is correct.