yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] decatf:
Can you check if your wireless access point is saved in the wifi config file?

Run the command line:

su -
cat /data/misc/wifi/wpa_supplicant.conf

It will show something like this. Where your wifi password is at the bottom part.

disable_scan_offload=1
driver_param=use_p2p_group_interface=1
update_config=1
device_name=Android_7276
manufacturer=samsung
model_name=p4wifi
model_number=p4wifi
serial_number=xxxxxxxxxxxxxx
device_type=1-0050F204-1
config_methods=virtual_push_button physical_display keypad
p2p_ssid_postfix=-Android_7276
persistent_reconnect=1
pmf=1
external_sim=1
key_mgmt_offload=1

network={
ssid="Your SSID"
psk="Your Wifi password"
key_mgmt=WPA-PSK
priority=11
}

Delete the file to reset the wifi config.

su -
rm /data/misc/wifi/wpa_supplicant.conf

Reboot and the wifi config will be recreated. Connect to your wifi access point again. Then reboot and see if it is being remembered.

It's the ROM. I wrote a new portion of the audio code. I noticed it is a bit lower.

The audio HAL itself is not supposed to be changing the volume. I think Samsung did some trickery with their original code to artificially boost the volume in software. I noticed this their open source code for other devices.

// We return an error code here to let the audioflinger do in-software
// volume on top of the maximum volume that we set through the SND API.
// return error - software mixer will handle it

This does not work with the newer Android audio API.
[Galaxy Tab 10.1 Android Development] davinaizer:
The AP data persists only during a session, after reboot it resets to default:

root@p4wifi:/data/misc/wifi # cat wpa_supplicant.conf
cat wpa_supplicant.conf
disable_scan_offload=1
driver_param=use_p2p_group_interface=1
update_config=1
device_name=Android_aba6
manufacturer=samsung
model_name=p4wifi
model_number=p4wifi
serial_number=XXXXXXXXXXXXXXXXXXX
device_type=1-0050F204-1
config_methods=virtual_push_button physical_display keypad
p2p_ssid_postfix=-Android_aba6
persistent_reconnect=1
pmf=1
external_sim=1
key_mgmt_offload=1
root@p4wifi:/data/misc/wifi #
[Galaxy Tab 10.1 Android Development] vidiot2013:
Another thank you

:) Just wanted to thank you Decatf for your fine work, and to everyone else who has contributed. This is the best ROM this old device has ever had!
[Galaxy Tab 10.1 Android Development] twhansen:
Super sweet an snappy ROM Many thanks!

I had a few problems with the 0109 release. After a dirty flash, Play services continuously crashed. I had to wipe everything and then it worked. Also Netflix is not working for me on this release. It worked fine on the 0101 release.

Thanks
[Galaxy Tab 10.1 Android Development] aamadorj:
I haven't seen any of those issues at my P4 running latest ROM with PA GApps for Lollipop. Everything is working fine, so far. Thanks a lot for this ROM, [MENTION=4404851]decatf[/MENTION].
[Galaxy Tab 10.1 Android Development] decatf:
Issue: Wifi access point not saved

Only some people appear to be affected by the wifi issue. The changes I made were intended to address Wifi Direct. With the 20150109 build I am able to scan for Wifi Direct devices but connecting with another Wifi Direct device fails. This change also appears to introduce this problem with access points not being saved.

Can you check the file permissions in the wifi config folder? Most of them should be "system wifi"

ls -al /data/misc/wifi/

Here are ramdisk images with some wifi changes reverted. It might resolve the wifi issue for those experiencing it.

p4-bootimage-20150109.zip

p4wifi-bootimage-20150109.zip
[Galaxy Tab 10.1 Android Development] jaibar:
Just flash the zip in recovery?
[Galaxy Tab 10.1 Android Development] davinaizer:
Here's the result:

root@p4wifi:/data/misc/wifi # ls -al
-rw-rw---- system wifi 21 2015-01-09 22:06 entropy.bin
drwxrwx--x wifi wifi 2014-12-16 11:06 hostapd
-rw------- system system 586 2015-01-09 18:37 networkHistory.txt
drwxrwx--x wifi wifi 2014-12-16 11:06 p2p_supplicant
-rw-rw---- system wifi 229 2015-01-09 22:06 p2p_supplicant.conf
drwxrwx--- wifi wifi 2015-01-09 22:06 sockets
-rw-rw---- system system 33 2014-12-16 11:14 softap.conf
drwxrwx--- wifi wifi 2014-12-16 11:06 wpa_supplicant
-rw-rw---- system wifi 370 2015-01-09 22:06 wpa_supplicant.conf
root@p4wifi:/data/misc/wifi #

I'll try the ramdisk ASAP...
[Galaxy Tab 10.1 Android Development] decatf:
Yes. Only init.p3.rc file changed.

This is in the boot partition. Or the RAMDISK. Or whatever it's commonly called. There's no need to repackaged the entire ROM. Just the boot partition
[Galaxy Tab 10.1 Android Development] davinaizer:
[MENTION=4404851]decatf[/MENTION], the boot image solved the problem. Now its remembering the Wifi AP.

Thanks a lot for your time and efforts.

About the bluetooth: I tested my BT headphone but can't get the sound to work. Is there anything i can check or should do to fix?

It pairs, but no sound from it.

Thanks again.
[Galaxy Tab 10.1 Android Development] decatf:
Was it working in the 20150101 build? In the 0109 there is only one change in bluetooth.

All of the official CyanogenMod devices were getting it merged into their ROM which is why I added it to this one too. You could actually try to revert part of the change if you know how to. If not then wait for the next build. I'll do one soon since this build seems to be causing problems.

Modify /system/etc/audio_policy.conf. Under the a2dp section change:

sampling_rates 44100|48000

to

sampling_rates 44100
[Galaxy Tab 10.1 Android Development] francisco.negromonte:
First of all, thanks a lot [MENTION=4404851]decatf[/MENTION] for the best ROM ever to run on my p4wifi!

Well, I don't know if this can help, but I think the problem with Wi-Fi losing its settings may have something to do with Backup & restore.

Backup account selection was greyed out when I was running 0101 build and I had no problem with Wi-Fi. The same after a clean flash of 0109 build.

After some googling, I managed to fix backup in terminal emulator with:

su
bmgr transport com.google.android.backup/.BackupTransportService

Now I can select my account in Backup settings, backup & restore work as it expected. But as a side effect Wi-Fi networks are lost after every restart,

unless I turn off backup

.

I really don't know why, but I hope this will help understand it.

Keep up the good work!
[Galaxy Tab 10.1 Android Development] timdoggg:
So is there any workaround out there or in the making?
[Galaxy Tab 10.1 Android Development] davinaizer:
I dont know if its related, but have yout tried the bootimage [MENTION=4404851]decatf[/MENTION] posted to solve the remembering problem?

http://xdaforums.com/showpost.php?p=58065833&postcount=484

---------- Post added at 01:59 PM ---------- Previous post was at 01:35 PM ----------

Yeah! Worked!

Will I have to edit this file again after flashing another build?

Thanks decatf.
[Galaxy Tab 10.1 Android Development] daformella:
Orginal Kernal

First off, amazing ROM, thank you for giving new life to the SGT 10.1. Im curious if you can upload the original kernel so I could flash it, I only use the Samsung keyboard dock. thanks in advance.
[Galaxy Tab 10.1 Android Development] decatf:
I don't know of a way to do it. It will take time to research this.
[Galaxy Tab 10.1 Android Development] francisco.negromonte:
Yes! It worked! Thanks!
[Galaxy Tab 10.1 Android Development] orkan95:
I tried to fix the backup issue with this. But was not successfull.

After keying in the code (with not error) the line for the backup account is still grayed out. If I now switch of backup and on again the line will turn black but nothing happens when I click on it. When I go back one level and come back to the backup&restore page the option "backup account" is gray again.

btw: I did a clean installation of the 0109 build together with the latest boot image and su2.4.
[Galaxy Tab 10.1 Android Development] francisco.negromonte:
For me It only worked after a reboot. Try to disable backup, reboot and then enable it again.
[Galaxy Tab 10.1 Android Development] orkan95:
Great, it works now. Thx a lot. You made my day!!!
[Galaxy Tab 10.1 Android Development] dlmetzger58:
Great ROM!

First off, thanks so much for a great ROM, my p4wifi hasn't been this zippy in a long time.

I dirty-flashed 20150109 on top of 20150101, and everything seems to be working, except the few glitches others have notices (losing the wireless password, etc.) But I've also noticed that the screen auto-rotate seems to be broken, you can toggle it off and on, but it stays in landscape mode regardless of the app running. Have others seen this? Interestingly, the auto-rotate icon is now on the status bar, and I don't remember seeing it there before.
[Galaxy Tab 10.1 Android Development] decatf:
Build 20150110

p4wifi-lollipop-20150110.zip

p4-lollipop-20150110.zip

p75xx-ICS-AudioHAL-20150110.zip

Changes:

revert Add 48kHz A2DP to audio policy

Fix WIFI access point not being rememberd

overlay: Add setting for dock audio and power control widget

Add ICS audio blob hacks to CM-12.0 frameworks av and build old ICS audio HAL for those that use it
[Galaxy Tab 10.1 Android Development] decatf:
Apologies to those 6 people that downloaded the p4 build so quickly. It was the wrong file. Please re-download.

The only thing missing was the WIFI not remembered fix.
[Galaxy Tab 10.1 Android Development] twhansen:
Thanks again for the super quick update.

I get this error when trying to install over the 0109 release.

E: error executing updater Binary in zip

Any tips?

Thanks
[Galaxy Tab 10.1 Android Development] honhan0904:
I think your downloaded rom get problem

Try redownload again

Hope it could help
[Galaxy Tab 10.1 Android Development] andreas_r:
I've downloaded the p4 ROM (10/01) twice and getting always the same error

So this is not the solution for me.
[Galaxy Tab 10.1 Android Development] mircea1965:
+ 1

same here!
[Galaxy Tab 10.1 Android Development] Grawol:
Thanks!

Just rooted my tab to install the 4.4.4, but came accross your release. Thanks! Everything working; a new tab indeed! One question though; I was hoping to use the tab with guitar effect apps, but still get a decent bit of audio latency. Could it be my mic/headphone splitter (just a wire splitt, no chip or batteries or anything), or is it a hopeless task for the 10.1 to handle audio in/out with a latency of about 25 ms? A bit off topic, but if anybody knows, it's probably one of you guys...

Tanks again!
[Galaxy Tab 10.1 Android Development] twhansen:
I have also downloaded several times. Same error.
[Galaxy Tab 10.1 Android Development] eushaun99:
After the error, go to advanced and select copy log to SD. Then look inside the log and see what it says.
[Galaxy Tab 10.1 Android Development] aduhai:
Me twice same error....
[Galaxy Tab 10.1 Android Development] orkan95:
me too
[Galaxy Tab 10.1 Android Development] decatf:
The p4 zip was mis-packaged again.

For this device we need to use an old updater-binary. One that supports the old script commands (set_perm, set_perm_recursive). So after every build I have to manually package those files before uploading.

I've tried it again. Let's hope nothing else is messed up this time.

p4-lollipop-20150110.zip
[Galaxy Tab 10.1 Android Development] vizkoze:
Fantastic Rom. My tab is actually very responsive. Tnx for your work.

Wifi issue is gone with 20150110 build on p4wifi.

The only issue I've encountered is a browser crash when playing embedded video on YouTube or vimeo.

I've tried on local videos with MX Player and it crashes when I use hardware acceleration. Maybe hardware decoding is not fully implemented?

Anyway, I love lollipop on this device. Fastest Android version I've ever used on the tab.
[Galaxy Tab 10.1 Android Development] orkan95:
Same issue here.

How can I deactivate hardware acceleration?
[Galaxy Tab 10.1 Android Development] decatf:
HW acceleration doesn't work in MXPlayer. It's been broken for me for a long time. Since Kitkat and maybe before that.

HW+ does work. It's not on by default in MXPlayer. Enable it in the app settings.
[Galaxy Tab 10.1 Android Development] JDog2pt0:
I'm having keyboard issue. When I flash the ROM, keyboard works. When I flash gapps (using PA Micro) the keyboard stops function. Going to try again with the gapps included here, but it's done the same thing too.

Keyboard issue being that it doesn't come up. On a wifi tab, using P4 wifi.

Nevermind. Included gapps worked
[Galaxy Tab 10.1 Android Development] decatf:
Yeah, that's why I haven't updated gapps since the first one posted. Something in the newer gapps packages is causing the stock keyboard to crash.
[Galaxy Tab 10.1 Android Development] andreas_r:
Hi Decatf, this fixed the issue. I was able to flash this file.

Thank you for all your effort.

Andreas
[Galaxy Tab 10.1 Android Development] mircea1965:
+ 1

same here! Thx
[Galaxy Tab 10.1 Android Development] twhansen:
Yep!! It's all honky dory now. Fantastic ROM! Best ever for the P4. Many many many thanks for the efforts and snappy updates.

One strange thing I have noticed. I play Kingdom Rusk Origins on my P4. The map looks very strange in the colors, it's all white with only a little bit of contrast. Otherwise the game works great. Any idea what that could be?

Thanks.
[Galaxy Tab 10.1 Android Development] twhansen:
Disregard this message and sorry for the spam.
[Galaxy Tab 10.1 Android Development] Lucas Kado:
p4 update: WiFi tethering w encryption and phone calls

First of all, [MENTION=4404851]decatf[/MENTION] thank you very much for your work. I haven't tried the ROM yet because I often use WiFi tethering and phone calls on my p4... yes I know it's a bit of an odd usage, but that's the way it is! :cyclops:

I was wondering if the issues with phone calls getting audio and WiFi tethering with encryption persists. It seems a lot has been changed for both audio and WiFi modules... maybe some p4 user could say a word about that :confused:
[Galaxy Tab 10.1 Android Development] ppickfor:
cifs manager not working

Great rom thanks for all your efforts.

cant get cifs manager to work though

Any chance of merging

http://xdaforums.com/showthread.php?t=2106480

Youtube seems a bit picked on 720 videos perhaps the hwaccel needs to beswitched off couldnt see how to do that though. Yotube videos sem to crash chrome but not browser
[Galaxy Tab 10.1 Android Development] vizkoze:
Indeed. Tnx for the clue.

Web video still crashes in browser and chrome. Audio works for a couple of seconds and then crashes the app... Minor bug if you consider the general quality of this room.

Tnx for your efforts.
[Galaxy Tab 10.1 Android Development] decatf:
Impossible to fix the Chrome video crash. Either Google fixes Chrome to support the Tegra 2. Or Nvidia releases source code for the bugged part of the video driver.

Neither are going to happen.
[Galaxy Tab 10.1 Android Development] timdoggg:
Who would be so kind to post a little walkthrough on how to overclock this ROM on this device. After some searching I saw SetCPU come up as well as some governors.

Just want to get the safest and recommended procedure as I actually have to use this device as my daily driver(thanks to the kind coding of decatf for such a beautiful rom) until my replacement phone arrives.

Edit:

Is this link any good? Will this work?

http://rootinghub.com/overclock-samsung-galaxy-tab-10-1/
[Galaxy Tab 10.1 Android Development] jaibar:
I used to be an optimization-control-freak, then I realized that too much tweaking eventually lead to system instability. So I stopped using "battery enlarging" apps, no more ram boosters, task killers, kernel superchagers and turbo injection bla bla.

Know what? Since then I enjoy stable devices, good battery consumption, no force closes nor random reboots.

My opinion/advice- leave governors and all that stuff stock values. If you feel you must, simply over clock CPU to 1200MHz- it's decent, and although many users will testify that 1400 or 1800 is excellent, not all devices behave the same. I know, same manufacturer, same model, same everything- it doesn't make sense- but true nonetheless...
[Galaxy Tab 10.1 Android Development] honhan0904:
Install no frill cpu from ch play

Overclock min 216 max 1200 for best stable.

This rom while good on performance so you dont need to overclock much.
[Galaxy Tab 10.1 Android Development] timdoggg:
Thanks, that was easy. Installed no frills and used the settings suggested, didn't change anything else. Currently observing
[Galaxy Tab 10.1 Android Development] Osirus71:
Are you guys clean flashing or dirty flashing these updates????:confused:
[Galaxy Tab 10.1 Android Development] jaibar:
I dirty flash.
[Galaxy Tab 10.1 Android Development] bert73:
24-12-2014 clean. All the newer roms dirty. No problems met.
[Galaxy Tab 10.1 Android Development] timdoggg:
just realize i might have been wiping my device unnecessarily...need to explore this dirty flash stuff next time...im new to this
[Galaxy Tab 10.1 Android Development] xonelith:
I've gotten into a habit of wiping cache, dalvik and system before each flash. I leave data intact and only need to reinstall any system files (like bbs or v4a). I don't think it's a dirty flash, but it's not a clean one either:)
[Galaxy Tab 10.1 Android Development] jaibar:
If not sure- ask. You'll never get flamed by asking this sort of questions.

If you read the OP and follow the couple of last pages in thread, you'll pretty much have a knowledge of what's going on with each new released ROM.

Best advice is to a) always have a fresh nandroid backup. These tend to occupy some storage size, so I usually keep only one or two fresh backups on device. Once in a while a keep one on PC .

b) if possible, check md5sum of the zip files you're gonna flash. To make sure the file is not corrupted. Bad downloads do happen.

c) The thumb rule is basically the same as going to the toilet: you wipe before you flush [emoji41]

However, although nobody will ever tell you that it is a bad idea to always make clean installs and wipe before flashing, it can be tiresome if the good guys release Roms every couple of days, which sometimes they do. It becomes tiresome to clean install every time.

So if it is just minor changes, I dirty flash without wiping anything. No brainer here- if something gets broken or not working, it can well be because of dirty flashing. That's when the backup becomes handy. Or a clean installation. And we have to remember that we can't complain if a dirty flash went wrong- it's our own fault.
[Galaxy Tab 10.1 Android Development] Wifflepig:
I wiped the device before flashing. Also I never updated the recovery. Used what I had on there, an older flavor of clockwork that I'd used when first rooting it. It worked fine.

The only thing I'm noticing is the front facing camera doesn't work. Rear does,but front is wonky and just produces a green bar pattern. Found that out trying to video chat with hangouts.

Other than that, its doing well. A tiny bit laggy from running on an older CPU,but that was expected .

Good job!
[Galaxy Tab 10.1 Android Development] Kaherdin:
Though dirty flashing is a working method, as [MENTION=3599815]jaibar[/MENTION] explained, it's a "rule" or at least wide spreadher truth that if you want to report a bug or a logcat you are asked to do this only if you are using a clean wiped device.

This applies for ROMs and FW in alpha and beta stages (as this is).

I'm a device-flashoholic and I usually do what [MENTION=3599815]jaibar[/MENTION] does - except for updates > one week [emoji123]
[Galaxy Tab 10.1 Android Development] CraKenDK:
Best ROM ever!

I just want to say this is by far the best ROM I have ever flash on my P4!

I tried Nameless ROM 4.4.4, which also was good, but lagged sometimes. Then I decided to try a lower version, in the run for better performance and went with SlimSaber Reborn 4.3.1. It was also good and speedy, but after some time it became unresponsive and needed a restart. Despite this ROM have some features which does not function, I gave it a try. I'm so happy I did! :)

My kids uses it every day for her Dr. Panda games... , Youtube, Netflix, Viaplay and just browsing.

Thank you so much :good: :)
[Galaxy Tab 10.1 Android Development] meanhacker:
amazing rom. kitkat roms never worked good on my device, i don't know why. they were very laggy and most of the times i had to wait like a minute for the tablet to wake up after pressing the power button. i always do clean installs.

This reminds me i have to change my signature lol
[Galaxy Tab 10.1 Android Development] morlong:
Hello!

Sorry for my english; i'm french

I can't flash gapps....

I installed TWRP 2830 P4 WIFI(01.01.2015) then ROM Lollipop (p4wifi-lollipop-20150110.zip). of course i wiped before and after and then i try to flash gapps (gapps-minimal-lp-20141109-p75xx) but it fail.....

Do you have a solution please?
[Galaxy Tab 10.1 Android Development] keki92:
try to do this: after instaling lollipop Rom, install gapps and wipe cache/dalvik cache, it, must work
[Galaxy Tab 10.1 Android Development] slpng:
The only time you should probably 'clean flash' a ROM is when you have been using a different ROM that saves settings in a different way or something else completely stupid. There's no point whatsoever in 'clean flashing' a newer version of the same ROM you are already using, unless it's explicitly mentioned that it now works differently, in that case you could end up with glitches due to leftover settings from the previous version you had installed. Really all you're doing by 'clean flashing' is just making the process longer and more complicated when in most cases it shouldn't be.
[Galaxy Tab 10.1 Android Development] stuckedinsweden:
Awesome to the max!

I bow my head and thank you kindly, Sir, for such a great and awesome ROM!

It really is a beauty for such ye old cutting-board! :)

Thank you again, and keep up the good and great job!
[Galaxy Tab 10.1 Android Development] meanhacker:
try redownloading the gapps. mine worked fine