yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] uli-hh:
I would suggest the following way:

If your ICS is not yet rooted do it with framaroot.

install SuperSU & BusyBox from playstore

backup your EFS with EFS-Professional (maybe you will need this if something goes wrong)

do a backup of your user apps & data (I recommend TitaniumBackup for this)

install this TWRP recovery with odin or odin-mobile

download Custom-Rom.zip file & G-apps.zip file and save them on external SD-Card.

boot into TWRP-recovery

do factory reset and wipe everything except external SD Card

install custom-rom (choose zipfile on ext. SD) will take more than 5 min!

do factory reset again

install G-apps (choose zipfile on ext. SD)

wipe cache/dalvigcache

reboot to system (will take several minutes)

install backup-app and restore you user apps & data

good luck;)
[Galaxy Tab 7.7 Android Development] aemee:
i got that same error when i first tried this rom.

i thought the zip was corrupted so i redownloaded it.

then i found out that the version of twrp i had was outdated.

all i did was flash the latest twrp and everything went smooth.
[Galaxy Tab 7.7 Android Development] massdown:
backup with EFS-Professional goes well with all partitions except the "factoryfs.img" , it takes all the free space on my tab (10GB) then failed :(

What is that mean !?
[Galaxy Tab 7.7 Android Development] uli-hh:
Maybe you better ask in the EFS-Professional thread:confused:

Have look at this "How to Backup and Restore EFS / IMEI on Samsung Galaxy Devices" on droidviews.com.
[Galaxy Tab 7.7 Android Development] ToastyZ71:
I'm running an i815 without SIM card.... would it be possible to have a flashable zip or option to disable the cell radio completely? Cell Standby takes up a good chunk of battery. (messing with airplane mode is a pain, especially with the wifi issues in this build)
[Galaxy Tab 7.7 Android Development] golfinggino:
Bluetooth is not working as soon as it is turned on the tablet restarts - hope you can post a fix - it is certainly the smoothest rom so far for this old tablet :)

Edit seems to work after it reboots I have moved this tablet to a full time gps for my car (didn't want to spend the extra $3000 to get the stock one) have it hooked up to a separate Bluetooth speaker not the one in the car and will test it out tomorrow I tried to buy a nexus 9 today to do the same job for a really good price and if I get it will test it out and see which size is better

Thanks for the great rom again!!
[Galaxy Tab 7.7 Android Development] massdown:
I can't find TWRP 2.8.2.x or above for my galaxy tab 7.7 , any help please ,?
[Galaxy Tab 7.7 Android Development] aemee:
http://xdaforums.com/showthread.php?t=2352967

its on the same page as this thread..

its like 8 topics below this one...

id have posted a direct link but i dont know which one you would prefer.
[Galaxy Tab 7.7 Android Development] ToastyZ71:
one of the mirrors:

https://www.androidfilehost.com/?a=show&w=files&flid=10302
[Galaxy Tab 7.7 Android Development] p3dboard:
Just testing the new build. Looks like the opengl es value is still set to 3.0, instead of the 2.0 value according to build.prop, so I assume that the device.mk would probably also have the opengles override set to the wrong value as well. I'll still test asphalt 8 though, in case the device. mk was updated by Daniel

Edit: latest build has the opengl es issue with Asphalt 8,because Asphalt 8 is an opengl es 3 based app, it tries to use extra features that are not present, but the build.prop file and device.mk file say are present. Once these settings are fixed, i believe that the game graphics will work properly
[Galaxy Tab 7.7 Android Development] philipnzw:
Way smoother than cm12.1

Seems promising
[Galaxy Tab 7.7 Android Development] p3dboard:
Es explorer bug that's present on cm 12.1 and Carbon rom is still present in omnirom. Sending a file via the send command to another es explorer on a different device crashes the rom.
[Galaxy Tab 7.7 Android Development] philipnzw:
Even the messenger app runs pretty decently on this ROM damn son

Btw can this ROM support RRO layers?
[Galaxy Tab 7.7 Android Development] daniel_hk:
I was testing the blobs from Mali-450. The line in device.mk just set the value in build.prop. If you think the value is wrong, you may change it in build.prop. Hoping it works for you.

Good luck.

S2 use a different Wifi chip. I don't know if stock rom support Wifi-direct. I was following the spec. in Jellybean.

I just updated the HAL driver. Might give another shot later. ;)
[Galaxy Tab 7.7 Android Development] p3dboard:
I tried setting the build.prop value to ro.opengles.version = 131072, but after a reboot it doesn't make a difference. It's the only opengles 3.0 game that i know of to test, but i don't really play it much, just reporting the fault. Not sure which mali blob the s2 is using, but would the official cm 12.1 mali blob be compatible with our galaxy tab?
[Galaxy Tab 7.7 Android Development] daniel_hk:
That's what I expected. I seldom play games. I don't think I can help. As before, I don't want to embarrass anyone. I was thinking you could find out yourself. What you believed might not be always true.

This is the second time I answer your similar question or imply. Again: "I don't care if I have credit nor won't hesitate to use the codes from other device." Not long ago, their developer ask me for the fix in H/W decoder. And I asked him for the torch in QS when my hard drive crashed.

S2 and our tab is similar but not the same. Actually, Note I is closer. But I don't have neither of them and what I can use had been already there for a long long time.

The only identical CPU and GPU drivers are there for 2 years. You may check the source from CM. The only "recent" change was made by me updating the kernel video driver from r3p2-01rel3 to r3p2-01rel4. That was 8 months ago. I got the source from official Mali driver for Linux. I changed the source to work with the existing only blob. Newer versions (eg. r4p0) can't even boot! :(

The blobs are the same for all Mali-400 devices. There is only one available. The only difference might be the resolution.

There are a few articles you may read. This was an old subject. People were looking for a solution years ago and none succeed yet. You can have these info. easily with a search engine.

The min. free memory settings are the basic tweaks since early Android. The values are highly device dependent. The default settings are from AOSP. For me, I rarely play games and gapps doesn't work in my region. I don't have problem with the default values.

There is the apk Performance Control (I modified from Omni), I have included in my other ROMs for 2 years, it can make some of those tweaks easily without direct edit. There's probably no definitely right or wrong values. It is part of the fun to tweak your own device.

You may dump the log to study if you are interested. It would be much better than wild guess. I can tell you, the time for syntax or figure correction are way way pass. ;)

I spent quite sometime to write and update the development guide thread for our device. Read it. It would probably answer most of your questions. I really hope someone might help. :)

Good luck
[Galaxy Tab 7.7 Android Development] p3dboard:
Thanks Daniel. I was just thinking today, i might read your build notes, and make up a development environment to build my own test versions. I do a bit of c#/c++ coding for work (Microsoft environment / apps), so i might give it a go, that way i could test idea's out. I've got a bit of a break coming early September, so i might see what i can do. I would love to be able to more actively contribute to helping you. Plus learn how to use the logcat outputs that they seem to use over in the s2 forum to track down and fix the bugs.
[Galaxy Tab 7.7 Android Development] p3dboard:
I just downloaded ubuntu 15 desktop, going to build a ubuntu vm for compiling, hopefully i can follow your build notes :)

Btw, the omnirom build feels very fast. I have adjusted the maxheapsize to 320mb and it's seems quite good. The animation setting in developer options was also set to 2,instead of 1. So after adjusting that redraws were much faster
[Galaxy Tab 7.7 Android Development] philipnzw:
Installed a bunch of apps ,build seems to be holding up well, sometimes it crashes randomly when watching YouTube

Using chainfire's recently app to reduce recent panel cards,omniswitch has something like slimkat's recent panel ,that seems to use less ram too

Considering to switch to lollipop now...

Also,is it possible to add slimkat recent to this ROM?
[Galaxy Tab 7.7 Android Development] sas_sas:
thanks Daniel..

This is the best of the best of LP roms for P6800..
[Galaxy Tab 7.7 Android Development] matoos:
hi.my tab have a slimrom version 5.1 and TWRP v.2.7.0.0.how can i update my tab to omnirom version.my first update please help me steps by steps
[Galaxy Tab 7.7 Android Development] p3dboard:
What tablet model do you have? Daniel hasn't built a Slim Lollipop build yet as far as I know, are you on Slimkat?
[Galaxy Tab 7.7 Android Development] Suf^fiX:
This is the fastest firmware ever since Android 3.2.

But it has two problems:

1) Bluetooth does not switch on :(

2) Flashlight does not switch off when in was enabled from taskbar.

This problems are absent in Carbon rom and CM. Could you please check the problems?
[Galaxy Tab 7.7 Android Development] daniel_hk:
I have tried a few more ROMs, including Slim. I simply don't have enough resource to release them all. My CPU is slow. It takes 5-6 hours for a clean build and my 1G hard drive is full from time to time. May be later...

It have been asked for too many times. A simple search would get thousands of answers in any language. :cyclops:

All custom ROMs are more or less the same to install for our tab.

1. update to latest TWRP.
2. download and copy the ROM zip (and gapps if needed) to sdcard. (int. or ext. sd are OK)
3. reboot to recovery
4. Do a factory reset. (Or format the internal storage if it hasn't been done for a long time)
5. Install the ROM (and gapps) (and latest SuperSUxxx.zip if you want to root)
6. Reboot

Slim 5.1 is an Android 4.4.2 ROM.

1. I don't have problem turning Bluetooth on.

2. It will be included in the next build

;)
[Galaxy Tab 7.7 Android Development] Suf^fiX:
It is strange. Carbon rom works with Bluetooth and previous omni rom worked, but current build turned bluetooth off just after it turns on. I am clicking on bt button it start enabling it and swith it off after several seconds. I have flashed firmware several times to carbon rom and back with no luck.

Please check this bug more. May be you need some log files from me?

When do you plan next update?
[Galaxy Tab 7.7 Android Development] ankjain:
double tap to wake

Daniel

only one request. Please include this awesome feature in your next build.

warm regards

ankjain
[Galaxy Tab 7.7 Android Development] sas_sas:
Thanks a lot Daniel..

I do not know the improvements after than previous Omni (Agu 04) but, I have a few quick observations;

- I can not get computer connection like previous release. I am not sure if it is my trouble only.. OTG works fine..

- Camera app force closes..

I have tried many Camera apps but none works out.. Any suggestion is welcome..

Daniel, is there any possibility of patch ?
[Galaxy Tab 7.7 Android Development] philipnzw:
Music players not working on 19aug build
[Galaxy Tab 7.7 Android Development] daniel_hk:
let me check. might be the fix of torch in QS.

CONFIRMED.

but I don't have problem connecting to computer or adb.

You may check if you have enabled debugging for your device:

1. connect the tab to a computer.

2 .turn OFF USB debug in Developer options

3. turn it back ON again.

4. I dialog box will be shown on the tab. check the box to enable your computer for debugging.

Good luck!

let me check.

CONFIRMED.

Omni have change the Samsung hardware library which is not working... I need to check why and what they have changed...

UPDATE: I have checked. Omni has make a pointer 64bit but our device is 32 bit. It caused crash whenever media server is called. Hence, Camera and media playback crashed. I have a uploaded a patch in post#1. Flash it in recovery will get everything back to normal. ;)
[Galaxy Tab 7.7 Android Development] sas_sas:
Computer connection is resolved when I followed up your method..

Ths again..

There are some audio and video problems I think..
[Galaxy Tab 7.7 Android Development] philipnzw:
Patch fixed it

Everything running smoothly for now got 1 random reboot
[Galaxy Tab 7.7 Android Development] sas_sas:
The same for me too...

Thanks again for your quick support..
[Galaxy Tab 7.7 Android Development] Suf^fiX:
I confirm bluetooth, torch and camera fixed.

All is fine now.
[Galaxy Tab 7.7 Android Development] akosiberber:
Performance settings is not working , it says "Root access failed or busybox was not found.

Any solution?
[Galaxy Tab 7.7 Android Development] p3dboard:
You need to flash supersu, omni doesn't have a built-in root
[Galaxy Tab 7.7 Android Development] snkchaos:
I'm testing i815.

So far Verizon 4G LTE connects but does not work correctly. It can go to google.com but any non-google websites like amazon.com or this website ends up being this message "net::ERR_NAME_NOT_RESSOLVED"

I'm guessing its the DNS not working correctly.

This is first rom that isn't stock that works with 4G LTE. I tried handful of roms and give up because 4G doesn't work. Good job.
[Galaxy Tab 7.7 Android Development] p3dboard:
If you install a Logcat program, like Log Cat Extreme from the playstore, and capture the log (in logcat extreme you hit the record button) while launching your browser and trying to access the URL's of the places not working (after that go back into log cat and stop the recording), you can capture some information which might help Daniel to work out the issue. Then you can attach the log to your post in the forum or send it to Daniel. In other rom development forums the logcat output has helped some of the developers to fix bugs.
[Galaxy Tab 7.7 Android Development] snkchaos:
Thanks. I tested out logcat but there is no log. It just says 0 lines when I press record and go to the web browser. DNS for 4G doesn't seem to work correctly. I tried to setup the DNS with an app to fix it temporary but it doesn't change the default.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I think the apn config file is missing.

I don't know if your system is rooted so I prepare a patch zip.

Flash this patch View attachment apn-patch.zip in recovery.

Please report if it work.

Good luck!
[Galaxy Tab 7.7 Android Development] snkchaos:
I tested it with flashing with recovery. Also did factory format and reinstall the rom without gapp and flash. Same issue.

Update

I tested again with gapp installed. I found out that I could go google.com or any website with google but not by the ip address for google. I tested ip address to make sure if DNS could be the problem.
[Galaxy Tab 7.7 Android Development] matoos:
please give me latest TWRP link
[Galaxy Tab 7.7 Android Development] daniel_hk:
It is a sticky thread now. Check the top of the forum.
[Galaxy Tab 7.7 Android Development] sas_sas:
Thanks again for the new release..

Is dirty flash enuf on to previous release ?

İf we make dirty flash is it necessary to flash gapps package too ?
[Galaxy Tab 7.7 Android Development] daniel_hk:
Gapps are on system. You need to flash gapps again. Anyway, it's the best time to upgrade the gapps too.
[Galaxy Tab 7.7 Android Development] curtislin:
I turn on WiFi ap, work fine for a few minutes then crash.
[Galaxy Tab 7.7 Android Development] LeonardoD93:
1 Question about new Update,when i download it,is there any way just to update it,so i dont need to reset everything,and delete the system over and over,when new update is out?
[Galaxy Tab 7.7 Android Development] daniel_hk:
I have been trying for 2 days. I tried starting hotspot for a few hours. I connected to it a few times with no problem and no crash. I didn't access internet much but worked fine for me every time.

Again, report with no detail doesn't help.

This is an all the time question. I can only tell you generally.

1. Same ROM update (eg. cm-12.1 to cm-12.1). Most likely no need to do factory reset. Just wipe cache & D-cache.

2. Same ROM different version (eg. cm-11.0 to cm-12.1). Usually no need to do factory reset. Wipe the caches.

3. Different ROM same version. Two cases,

a. AOSP based to CM based or vice versa (eg. Omni5.1 to cm12.1). Usually a factory reset is required.

b. Same version, AOSP based to AOSP based OR CM based to CM based. (eg..cm-12.1 to Carbon5.1). Usually, factory reset is NOT required. Wipe the caches. If you can boot up. Clear the data of the app settings would be enough.

Other than the above, factory reset is most likely required.

Most of the ROM will format the /system partition before writing. Normally, you don't need to wipe it separately.

However, custom ROM usually don't touch /data, A factory reset (wipe /data and /cache) before or after flash is the same.

That means we can try booting without factory reset first. If it can boot, sometimes clearing the data of a few google sync apps would fix the error dialogs. If bootloop, reboot to recovery and do a factory reset.

If you have been using a ROM for a long time. Wipe the caches would speed up the system.

Format data would clear any residues of the old systems/apps. It also help defragmentation of the files in sdcard.

IN ANY CASE, it is a good habit to backup (better to ext. sdcard) before flash. Most of the devices backup /data by files. That means a restore would recover fragmentations too.

To all, I hope these would clear things up.

Good luck!
[Galaxy Tab 7.7 Android Development] so_ang:
Wish P6800 Still hav Amdroid M Base [emoji713]
[Galaxy Tab 7.7 Android Development] p3dboard:
It shouldn't be too long, Android 6.0 is being merged into the Omnirom source - example https://github.com/omnirom/android_art/tree/android-6.0, but the complete Source Tree is not done yet (https://github.com/omnirom/android) as you can see the master repo for Android 6.0 is not yet available. Once that's done, Rom builders can start compiling.
[Galaxy Tab 7.7 Android Development] curtislin:
hi, Daniel

I test wifi ap again. Wifi ap functions well if client devices did not consume internet packets. Once client connect to internet through wifi, P6800 crashed in seconds.

I tried to catch error messages through logcat, but USB device is not functioning. My PC cannot detect P6800 when usb cable plugged, no ADB, no MTP...

Hope information helps.
[Galaxy Tab 7.7 Android Development] LeonardoD93:
Just to report the Bluetooth dont work.
[Galaxy Tab 7.7 Android Development] xaadilhx:
The most stable release I've tried since official jelly bean. I can confirm most daily tasks work, Wi-Fi, mobile data, camera, phone etc.

I've had a few freezing requiring reset & tested hotspot, I can verify curtislins error where the device will reboot after connected device makes some data requests in 1/2 minutes.

Overall fairly stable, where others are rather sluggish with any increased multitasking.

One main thing I couldn't do, send files, upload to cloud apps, seem to completely freeze the device.
[Galaxy Tab 7.7 Android Development] biopsin:
borked bluetooth

.. log
[Galaxy Tab 7.7 Android Development] Boundlessua:
Need some help installing OmniROM.

After wiped (data/cache/dalvik cahe) and formated system/prelink - I've tryed to install latest OmniROM and got such error:

Any ideas what went wrong ?

(Recovery I'am using - CWM 6.0.2.3)
[Galaxy Tab 7.7 Android Development] LSD DREAMER:
Use TWRP to flash. Much better recovery
[Galaxy Tab 7.7 Android Development] Boundlessua:
Is it possible to flash TWRP recovery from CWM recovery ? :confused: Or Odin only ?
[Galaxy Tab 7.7 Android Development] LSD DREAMER:
I prefer Odin. Use Odin mobile. Quick easy and effortless
[Galaxy Tab 7.7 Android Development] Boundlessua:
BTW - 5Ghz Wi-Fi not working on this ROM. Should be added to the list.

Just before this ROM - I used 4.1.2 and it worked fine on 5Ghz.

Update.

After some reboots and google services update - it started to work 0_o
[Galaxy Tab 7.7 Android Development] biopsin:
bluebork

does anyone have any files in following folders

/data/misc/bluedroid

/data/misc/bluetooth

/data/misc/bluetoothd

also tried "service call bluetooth (1-10)" but no bluetooth service exist.
[Galaxy Tab 7.7 Android Development] QuiQuos:
Guys is just mine or this ROM is very laggy??

I Think all 5.0+ roms are laggy no?

I had 4.4 and it was very fast

Is there any way to get this rom faster??
[Galaxy Tab 7.7 Android Development] p3dboard:
Android 4.4 is probably the optimal for speed / responsiveness with generally no lag. I think the Android 6.0 Rom's are less laggy then Android 5.0 and 5.1, but they still have some lag as from Android 5.0 and onwards, their seems to be a greater memory overhead. I just got an Nvidia Shield tablet, it it absolutely flies on Android 5.1.1. It has 2Gb of ram though.
[Galaxy Tab 7.7 Android Development] jasonhs:
Anyone managed to get the bluetooh to work on final release 2015/9/26? Whenever i turned on, it off by itself after few seconds.
[Nexus 6 Q&A, Help & Troubleshooting] wright_ac:
So my phone shows the Android 5.1 Factory Image I flashed as having;

Baseband Version - MDM9625_104446.01.02.95R

Kernel Version - 3.10.40-geec2459 android-build@vpbs1.mtv.corp.google.com #1 Wed Jan 28 22:14:35 UTC 2015

Are these correct for Build Number LMY47D?
[Nexus 6 Q&A, Help & Troubleshooting] Casper34:
http://xdaforums.com/showthread.php?t=3055705

Sent from my Nexus 6
[Galaxy S 5 Q&A, Help & Troubleshooting] ezyandy:
Folks,

Strange one. Just upgraded to Lollipop 5.0 and now when I move out of range from a WIFI access point, my phone DOES NOT automatically switch to mobile data. Previously on KitKat 4.4.2, where this would occur automatically.

Strange thing is that when I manually switch off the WIFI transmitter on my phone, it then switches to mobile data.

Don't want to have to do this all the time when I'm out of range!

Any advice would be great.

Thanks in advance.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Mine did that once, clearing cache from recovery and rebooting the phone fixed it

Turn off smart network switch too from wifi settings
[Galaxy S 5 Q&A, Help & Troubleshooting] ezyandy:
Cheers.

Will give this a try.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Also remember that after upgrading from KK to LP, leaves a load of rubbish files behind from KK that cause all sorts of problems, it is highly advised to factory reset after upgrading, you'll find most people here have done that and it solves a majority of problems
[Galaxy S 5 Q&A, Help & Troubleshooting] ezyandy:
Ok cool.

Looks like I might have to do this.

Have tried clearing cache from recovery and have also disabled autoswitching - still getting the same issue.

Will try a factory reset.
[Nexus 5 Q&A, Help & Troubleshooting] cthulu:
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609
[Nexus 5 Q&A, Help & Troubleshooting] zagorteney:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
[Nexus 5 Q&A, Help & Troubleshooting] cthulu:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want ;)

So my problem manifests like this:

boot phone

camera seems to be working (opening camera app doesn't crash but actually allows taking pics)

after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"

reboot fixes it for another few minutes
[Nexus 5 Q&A, Help & Troubleshooting] zagorteney:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
[Nexus 5 Q&A, Help & Troubleshooting] PHPanos:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
[Nexus 5 Q&A, Help & Troubleshooting] zagorteney:
And this was happening immediately after booting your phone? Then must be hardware. ?