yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] takaeshi:
3G data improve and supported ?

May i checked if 3G data improve and supported ? Love the rom so much but ended up it shown please insert my sim card. Could someone please enlighten me , much appreciated for the hard work Daniel ! Good Job ~

I'm using P6800
[Galaxy Tab 7.7 Android Development] regentonne:
so, maybe stupid question, but:

when checking for update in "system settings -> about phone" it tells me i got newest software (20140503)... so old one...

do i have to flash update manually and afterwards everything from before is "lost" and i have to configure all new? or is it really just an update and nothing gets lost?!
[Galaxy Tab 7.7 Android Development] raducux:
I dont think the ota update in settings works because this device is not officially supported .
[Galaxy Tab 7.7 Android Development] regentonne:
for network stuff I really like "es file explorer"...

" next browser " seems to work without distortion... I use that one on my androids and I like it...
[Galaxy Tab 7.7 Android Development] hogig:
exfat

Hi there Lt. Col Johncross,

Sorry, I am confused about this post and then a latter a post about exfat not supported...

I run TWRP and I can install the 4.4.3 omni and gapps from a exfat 32gb microsd just fine. it is that running omni in the phone, the microsd is not detected... are you saying that with your microsd formatted as primary in exfat, omni can read exfat formatted microSDs fine?

Many thanks,
[Galaxy Tab 7.7 Android Development] hogig:
Hi there,

A fellow HKer testing your latest build. Many thanks Daniel.

I am wondering if anyone's having issues with the camera apps? I get a blank screen trying to load them up. I have installed clean 4.4.3 Omni with Gapps 4.4.3 set.

Many thanks.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Hi, Fellow citizen! :D

I just checked and didn't have issue in the built-in Camera app and Instagram.

Sometimes the old backup data might not be compatible with the new system.

If you use apps from restoring (eg. Titanium BU), try "clear data" in "settings > apps".

Good luck!

As a responsible HKer, vote on 622! :cowboy:
[Galaxy Tab 7.7 Android Development] p3dboard:
Location Services issues

Does anyone have issues with location services? I have just installed the 4.4.3 rom, coming from a 4.1.2 bodivas rom, i am using a p6810.

I have tried high accuracy, battery saver and device only. Any ideas on how to get location services working? Google maps can't locate me, weather apps can't find their location.

Thanks Daniel for your work.

Peter

Edit:

I reflashed the rom over itself again and this has fixed location services
[Galaxy Tab 7.7 Android Development] 3l1k:
have no problem with camera app on i815
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
exfat reply

I had to fall back to cm10.1 for data purposes on my i815. I think I ran paragon to get exfat support

link

https://play.google.com/store/apps/details?id=com.paragon.mounter
[Galaxy Tab 7.7 Android Development] regentonne:
so, some how my DSP manager seems to work not... don't know why... tried stream, tried mp3 out of my home network... tried many equaliser settings... but I don't hear a difference... any idea why our what to do?

thx
[Galaxy Tab 7.7 Android Development] p3dboard:
I did a bit more playing around as I was using cyangenmod for the last day, then i came back to omni. It looks like Gps signal works fine for location services, but wifi / networks can't provide a location. Any idea's on how to fix the wifi location services mode?
[Galaxy Tab 7.7 Android Development] p3dboard:
According to this xda post (http://xdaforums.com/google-nexus-5/themes-apps/gapps-t2012857/page226) I might need NetworkLocation.apk, which I have confirmed is missing. I just have to find a copy of Google Apps (the Paranoid Android one didn't have it) to copy to the /system/apps folder.

I have also found that third party apps don't seem to have permissions to access Location serviecs, eg Viber, instant messaging, can't access the location services if I want to send my current location. It asks to turn on location services, which is already turned on.

Found another post on this issue http://xdaforums.com/moto-x/orig-development/rom-cyanogenmod-11-moto-x-t2719646/page10

Anyone got a solution?
[Galaxy Tab 7.7 Android Development] raducux:
This last build has a great battery life . no leaks at all. Just 1hour and a half of screen on....but still, amazing compared to last build which was quite battery hungry.
[Galaxy Tab 7.7 Android Development] p3dboard:
Looks like someone figured out how to fix it. Daniel are you able to incorporate this fix?

https://github.com/LiquidSmooth-Dev...mmit/4df724fdd9cec576a80deb72d1574ea1fef26bb9

I found this link on a post from Today's date in the xda forum thread I posted above for the moto x do cyangenmod rom. It's from the Liquid Smooth rom, which is a slim rom based rom
[Galaxy Tab 7.7 Android Development] daniel_hk:
No. I don't think I can fix that. There is nothing to fix.

I was thinking you would figure it out but you are baking on the wrong tree.

If you need a Google service, all you need is flashing the gapps after the ROM. Copying files to system is not the proper and right way.

Goof luck!
[Galaxy Tab 7.7 Android Development] p3dboard:
Thanks Daniel for replying.

I already have google apps installed, the PA gapps. The fusedlocation.apk file in priv-apps is providing location information to google apps, but only in high accuracy mode or device only. Battery saver location mode, which uses wifi can't provide any location information to google apps like maps or Google now.

There is also the issue that non google apps can't access location information at all, whether in high accuracy mode or any other mode, device only, battery saver etc. 3rd party applications say location services is disabled.

The networklocation.apk is part of older google apps packages, but the 4.4.2 and 4.4.3 packages don't seem to use that any more, it used to live in /system/app.

If you put location services in battery saver mode, you can see if google maps can locate your current position.

Thanks, Peter
[Galaxy Tab 7.7 Android Development] L_o_k_i:
[MENTION=5495967]p3dboard[/MENTION]

Hi,

I have exactly the same problem as you. The Google apps are installed (pa_gapps-stock-4.4.3-20140608-signed.zip). So I took networklocation.apk from pa_gapps-full-4.2-20130710-signed.zip and paste it in system/app, reboot in recovery, delete dalvik cache and voila !!!
[Galaxy Tab 7.7 Android Development] p3dboard:
Thanks Loki,

I was just missing the wipe dalvik cache step. Location services is now working properly with the gaps 4.2 network location. apk in /system/app.

3rd party apps are now able to get location services!

On another note, if you install ea games like real racing 2, Fifa 2012, and get an error about not being able to contact a download server, you need to set the lcd density in /system/build.prop to 160, instead of the rom default of 182. After you download the game content, you can put the lcd density back to 182 if you prefer the icon size. I tried using xposed module App Settings, setting it to 160 dpi, but the ea games must check the build.prop file, so you can't do it via xposed, unless there is another trick I missed.
[Galaxy Tab 7.7 Android Development] L_o_k_i:
Unfortunately my solution doesn't work anymore and I don't know why... Clearly there's a problem with this build because on other devices running android 4.4.3 there's no need for networklocation.apk to be able to use battery saver location mode.
[Galaxy Tab 7.7 Android Development] p3dboard:
Hi Loki, after testing a bit more, the networklocation.apk trick only seems to allow third party apps to access location data while in High Accuracy mode.

Battery saver still doesn't seem to work. Google Apps also can only access network data in high accuracy mode.

Possibly that link to the moto x fix might be worth investigating. I am not sure which apk file they are referring to about the overlay file that needs to be modified. But two lines need to be commented out according to that.

Daniel - I could be on the wrong track, just putting some ideas together

I found this post about possible locations for default values, the overlay seems to be a device specific config settings file, so our one would obviously be different from the moto x one. The page link below has possible other locations.

http://stackoverflow.com/questions/16770639/how-to-set-default-properties-in-aosp

I also found some code comments about the purpose of those config.xml file settings

http://grepcode.com/file/repository...rameworks/base/core/res/res/values/config.xml

<!-- Whether to enable network location overlay which allows network

location provider to be replaced by an app at run-time. When disabled,

only the config_networkLocationProviderPackageName package will be

searched for network location provider, otherwise packages whose

signature matches the signatures of config_locationProviderPackageNames

will be searched, and the service with the highest version number will

be picked. Anyone who wants to disable the overlay mechanism can set it

to false.

-->

<bool name="config_enableNetworkLocationOverlay" translatable="false">true</bool>

<!-- Package name providing network location support. Used only when

config_enableNetworkLocationOverlay is false. -->

<string name="config_networkLocationProviderPackageName" translatable="false">@null</string>

<!-- Whether to enable fused location provider overlay which allows fused

location provider to be replaced by an app at run-time. When disabled,

only the config_fusedLocationProviderPackageName package will be

searched for fused location provider, otherwise packages whose

signature matches the signatures of config_locationProviderPackageNames

will be searched, and the service with the highest version number will

be picked. Anyone who wants to disable the overlay mechanism can set it

to false.

-->

<bool name="config_enableFusedLocationOverlay" translatable="false">true</bool>

<!-- Package name providing fused location support. Used only when

config_enableFusedLocationOverlay is false. -->

<string name="config_fusedLocationProviderPackageName" translatable="false">com.android.location.fused</string>
[Galaxy Tab 7.7 Android Development] p3dboard:
I had a similar problem, when i opened google play music the dsp manager would report it had crashed, and in other apps no difference seemed to be occurring.

So i extracted the dsp manager from the slimkat rom as it was version 2.0, which is working fine on another device i have with Android 4.4.3, the slimkat rom is also compiled by Daniel, and using Es Explorer with super user rights, i replaced the /system/app copy of dsp manager, reset the file permissions to rw-r-r on the dsp manager.apk file. Then i rebooted into recovery manager and wiped the davlik cache and rebooted. After that dsp manager is now working fine for me.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Having the World Cup fever lately, didn't check the forum... ;)

I was on my Carbon 4.4.3 test build when you tell me that. That Carbon build doesn't have problem in locationing so I assume it was a Gapps stuff. I re-install my Omni today after seeing your posts. Yeah, there is locationing problem in my Omni 4.4.3.

A few points to note:

1. The app NetworkLocation was replaced by FusedLocation since 4.2.

2. FusedLocation is part of the frameworks_base now. The code is almost the same as NetworkLocation.

3. FusedLocation will be installed automatically as private apps.

4. The commit you mentioned for Moto is to remove the default "false" values for locationing. It didn't appear in my device tree so is not needed. Actually, this value will be asked in the startup app (after factory reset). I don't know why they have two default values. KK only has FusedLocationOverlay.

There hasn't been any change in the locationing code for a long time (> 6 months). I think it didn't start at boot for some reason. I need to check why it doesn't work on my Omni. Sorry, it would be after the World Cup... ;)

In the mean time, do whatever you think working for you.

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

Enjoy the WC!!!
[Galaxy Tab 7.7 Android Development] regentonne:
good to know, and finally someone answering ^^

would it be possible for you to send me your dsp manager.apk?! so i have one i know of to be working... greets
[Galaxy Tab 7.7 Android Development] p3dboard:
Version 2.0 is attached. The omni rom build has version 2.1
[Galaxy Tab 7.7 Android Development] p3dboard:
Multi Window via Xposed

Hi Guys,

Some of you probably know this, but if you have the Xposed framework installed, you can enable a multiwindow support (not as good as Samsung's implementation, but its something).

1st of all for this rom you need this Xposde Module, otherwise you can only see one of the Multiwindow apps at a time

[FIX][XPOSED][KK] Fix visibility of multiple non-fullscreen activities

http://xdaforums.com/xposed/modules/fix-fix-visibility-multiple-fullscreen-t2682352/post51104521

Then the second module

[APP][Xposed] XMultiWindow

http://xdaforums.com/xposed/modules/app-xmultiwindow-1-6-0-omnis-splite-view-t2641967

Edit: Found a better Multiwindow Module in Xposed - XHaloFloatingWindow

It supports almost all the functionality of the Samsung Multiwindow, you can have floating Windows, as well as Split screen (by Snappingitems to Top or Bottom), you can also enable an option so that in the Task Manager - you can long press an item (like in Mokee rom below) and add to Halo, and the items become floating multi window apps.

I don't know how good the Omnirom multiwindow patch is, but you don't need to patch to use this one.

Not sure if Daniel might be able to build us a copy of Mokee Rom, as I have this on my Galaxy S2 phone (http://xdaforums.com/galaxy-s2/orig-development/rom-mokee-opensource-project-t2512495) - its already up to Android 4.4.4 on my S2 phone and gets OTA updates. Its built on ASOP & Cyanogenmod (its got the theme Engine) and it has multiwindow built in as well. From the Task Manager you can just turn on multiwindow for any open app, by long pressing them and choosing add to Split View. Its running on Tablets like the Galaxy Tab 2, Galaxy Note 8.
[Galaxy Tab 7.7 Android Development] hogig:
Unfortunately, the process com.google.process.gapps has stopped

Hi all,

Did a quick search, not sure if this is common knowledge or not: is there a reason when the "Unfortunately, the process com.google.process.gapps has stopped" keeps popping up?

Many thanks.
[Galaxy Tab 7.7 Android Development] p3dboard:
Which google apps package did you flash? I used the Paranoid Android (PA) Android 4.4.3 package and have not had this issue.
[Galaxy Tab 7.7 Android Development] bessie31:
Disable Cell Standby

On my i815, Cell Standby seems to be draining the most juice (60-80% of battery usage, drains the entire tab with no usage at all in about 30 hrs)

Anyone have any idea how to turn it off? (tried airplane mode, removing SIM, etc.)
[Galaxy Tab 7.7 Android Development] 3l1k:
I have this problem too but can't solve it. I try to disable all phone related services and even remove it but cell standby still eat my battery. So i think it is kernel problem and maybe Daniel will fix it after world cup
[Galaxy Tab 7.7 Android Development] xaadilhx:
experiences .... I've had this installed for about 2 days but I've been having serious battery issues. I came from the Official Jellybean via cwm. Did all the reset, wipes etc.

Initial reboot was to a black screen after the first boot screen. I did a reboot after 5 minutes, it got stuck a few times but I believe its sorted itself out now somehow. Google+ & the xda app initially killed 50% overnight when the device is supposed to be in deep asleep. Since removing the apps, battery drain has slowed however I've lost 20% today with no use in just under 4 hours. Memory can get quite low at times and performance isn't as I'd hope for kitkat.

It seems hit or miss, I'm not sure what's causing it. Now its just Android OS & Screen at the top battery user but its still draining significantly faster than normal JB. I'll observe and use further to see if it sorts itself out like the bootup. I'd really like a stable fast rom without needing a quad core upgrade.
[Galaxy Tab 7.7 Android Development] p3dboard:
Something is not quite right. On my p6810, i get less than 1% drain in 12 hours if i leave the screen off but the tablet still on. Have you checked the wifi settings? I think by default it has constant scanning turned on for wifi networks, for Google location services. Turning that off from memory also helps. I also find wakelock detector from the play store helps in tracking down the battery drain apps
[Galaxy Tab 7.7 Android Development] daniel_hk:
MoKee is from China, I have played with it on my p6800 for sometime. I don't have enough space to hold too many roms and someone complained that too many builds misled them. Therefore I haven't release them all. I plan to post some for testing later but I can't keep all models.

Seems there is something wrong with 4.4.3. Google jump to 4.4.4 just after a few days. Battery consumption is much better with 4.4.4 in my Nexus 4.

See if the Tips in post #2 help.

Good luck!
[Galaxy Tab 7.7 Android Development] xaadilhx:
Thanks for your comments, p3dboard & daniel_hk. I checked all settings and somehow after the initial power drain, it started draining normally. Performance has stabilised but I'm still not sure of the cause outside google+ & xda apps or why these apps could suck the battery dry so quickly. At one point when this was going on I had the charger plugged in and the battery was reducing like mad. I never saw a battery drop like 10 % in maybe 3 minutes like that. Since its working fine now, I've been loading all my apps to see how it handles, so far I've noticed some bottlenecks and slight screen tearing while using task switch.

Obviously there are some issues with apps/gapps, getting away such a hunger with battery, like google+, perhaps it was the package, I remember it was mentioned not to use minimal install of some versions.

About Mokee, and all the rest, There are so many roms and they all take very much time and resources to get working, although its interesting to flash a rom and use different features it can be stressful, I would think most would prefer stability first to run all popular apps. So instead of pac, beanstalk, cm11, slimbean etc which are all from different mod sources with different features. This all sounds like too much repetitive work mixing code which can have such random effects. Great work, getting wifi, bluetooth and mobile / data sorted of most of them.

I'm just thinking out loud like back to when I had my samsung Omnia HD with nokia symbian, eventually all the developers had to retire and move on. Yes android is popular, but how long will our device live. Maybe I should say how capable is a 1.4ghz dual core cpu with 1gb of ram on our tab. If I have installed skype, magic jack, upptalk, facebook/messenger, google voice, hangouts, viber etc... can we really get smooth performance with so many apps that might be in the background along with other messaging, launchers, security suite, power saving apps, etc. Jellybean official was ok, just a little slow at times.

Can we not just ask, which is most stable/light and focus on that one only instead of upgrading all the time? Do we always need 4.4./1.2.3.4?

If we need all of those, then some of us will probably go out and buy the Tab S 8.4 & keep buying new Samsung devices every 2 years.

I personally want my 7.7 working for another 2 years, just a bit better than 4.1.2 Jelly bean! Support? Comments?
[Galaxy Tab 7.7 Android Development] p3dboard:
Well just a little comment on the last item. Android 4.4.4 was released in part as a security fix for some components, eg Openssl. So the updates sometimes are to make our devices secure from being hacked, or our data from being intercepted by malicious people. Unfortunately because older devices don't get these updates from manufacturers, they can become more vulnerable to malicious attacks.

The various Roms have different features, produced as addons to Android, just like many manufacturers modify Android. So its about choice, but that can be confusing, if you just want a stable system, which to pick. Mokee rom for example, supports the exfat file system, which Samsung devices normally support for 64gb memory cards. You can reformat the 64gb cards to fat32 file system for other roms, but with Mokee you don't have to. Mokee recently got a better lockscreen notification system that is very similar to the next version of Android, the L one, possibly lollipop, it wouldn't surprise me if google in part copied the idea.

Cyangenmod based roms have a great theme engine, that allows you to easily change the look and feel of Android. Some people like to do that, like repainting your car. Others are just happy with the manufacturers basic colours.

Thanks to Daniel though for keeping our tablets alive. Consider the age of the device its still going well. A galaxy tab 3 8inch only has a 1.5ghz dual core chip, so it's not much different from our tablet. Eg on geekbench our tablet gets a score of 411, the tab 3 8 inch gets a 426. So its still a good tablet for its age
[Galaxy Tab 7.7 Android Development] p3dboard:
Microphone in video capture not working

Don't know if anyone else has tried video capture with this rom, but i did tonight. It captures 1280x720 video fine, but it's all silent. I tried stock camera and another app called a better camera. But no audio.

Google now can hear my voice, so the microphone is working. Any ideas? Is it an issue with the profiles.xml that define the video and camera settings?

Peter
[Galaxy Tab 7.7 Android Development] xaadilhx:
I've just testing video recording in all resolutions, I can confirm there is no sound recorded whatsoever. Didn't notice before because I didn't try out the video recorder before
[Galaxy Tab 7.7 Android Development] p3dboard:
Daniel's supplied the fixed / updated audio config file in the Cyanogenmod Rom thread, I have tested it and fixed the audio capture for me.
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
Happy independence day to HK - Did you walk??

Shame the USA lost today - Oh well - Maybe one day?? **** it GO COSTA - DOWN with the NETHERLANDS!!!!!!
[Galaxy Tab 7.7 Android Development] so_ang:
In future U still has Android L for P6800 ROM or it only KitKat ???
[Galaxy Tab 7.7 Android Development] NakedFaerie:
This is awesome. I thought the device was dead and nobody made roms for it anymore. Thanks :)
[Galaxy Tab 7.7 Android Development] stonedraider:
just installed this rom. looks very nice.

anyway there seems to be no su-binary and superuser installed (tried to do so trough play store but busybox installer and all fail because of no root access).

i flashed the rom another time (full wipe of course) but it keeps in this non-root-state.

could this be related to an old recovery i am using?

other than that the rom runs fine...
[Galaxy Tab 7.7 Android Development] NakedFaerie:
For me it says its rooted but no root access. It wants to update SU but refuses. I dont have a clue whats going on. I guess we'll have to wait for the next release to run our rooted apps. :)
[Galaxy Tab 7.7 Android Development] 3l1k:
Just flash Update-Super.zip from cwm and will be happiness
[Galaxy Tab 7.7 Android Development] dfkt_:
Best to use the newest original file, straight from the developer: http://download.chainfire.eu/supersu
[Galaxy Tab 7.7 Android Development] NakedFaerie:
That worked. :) Now I have SU working.

Glad to see the Tab 7.7 back to life with a new OS for it
[Galaxy Tab 7.7 Android Development] jun4:
after update 4.4.4 my google keyboard stopped.. how to solve this?
[Galaxy Tab 7.7 Android Development] so_ang:
Really lov this Rom but cant access my exFAT card. T_T
[Galaxy Tab 7.7 Android Development] raducux:
I keep geting weird collors sometimes. the blue inverts to pink...and all colors seem to be banding.

I have to reebot every time for it to go to normal