yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] alroger:
SuperSU

I noticed that if we flash SuperSU again after updates, it looses it's configs and you have to re-authorize every app. But the latest SuperSU, 1.94, asks you if you want to install a script so it keeps installed between ROM updates, and that seems to work fine. After agreeing to the install of that script, no need to flash SuperSU anymore between ROM Updates.

About the ROM Apps that come back, I use Titanium Backup, and have them Labled "bloat". So right after every update I just ask it to batch uninstall bloat.

There are other apps to do this also.

Cheers! Great ROM!

Every sensor working.... and still Google Camera won't show PhotoSphere for me... anyone got that working? (p1n here) Is it because it:

"Photo Sphere, Panorama, and Lens Blur require at least 1 gigabyte of memory"?

EDIT: I use /OpenDelta/FlashAfterUpdate/ to put the Xposed .ZIP installer, so I don't have to reinstall it every update. Just use the Manual ZIP method of install and find and copy it's ZIP in /sdcard/Android/data/xxxxxx.Xposed.xxxx.
[Galaxy Tab  Android Development] RogerG:
1gb memory can't be the problem if it's not working on p1n - photosphere has been working (on and off) for quite some time on p1. in the latest roms, you need to to set ro.config.low_ram=false in /system/build.prop, maybe that works for p1n as well?

(see metterschlings recent post)
[Galaxy Tab  Android Development] alroger:
PhotoSphere on Google Camera

Cool, thanks! ro.config.low_ram=false makes all the functions appear in the camera. It works, expect PhotoSphere and Panorama are 90deg offset. I'm gonna try to play around with that.

EDIT: It works... I just have to disable Rotation Lock (from Quick Settings), start it in Portrait, then I'm able to freelly rotate and works!
[Galaxy Tab  Android Development] RogerG:
well, glad that for once I could help one of the gurus :D

thanks for all your hard work!
[Galaxy Tab  Android Development] nhojeric214:
i cant install any other roms! what possibly go wrong? everytime i flash a rom it says:

assert failed: run_program ("/tmp/updater.sh") == 0

please help i think my tab is soft bricked T_T [MENTION=4101982]alroger[/MENTION] [MENTION=3031478]humberos[/MENTION]
[Galaxy Tab  Android Development] white-energy:
[MENTION=3031478]humberos[/MENTION]: this might be really interesting :))

http://xdaforums.com/showthread.php?t=2754997
[Galaxy Tab  Android Development] humberos:
Hi dude!!!!

Nice to see you here!

So, try to check this option:

Settings --> Performance --> Advanced Settings -> Force high-end graphics.

I think if it works then it will be an easy way to do this.

Inté!
[Galaxy Tab  Android Development] humberos:
Please check your download install file.
[Galaxy Tab  Android Development] humberos:
humm!!!

I will check it when I get mtd driver back ported.

I think it will increase tab booting speed but I have a lot of patches to see....... T_T
[Galaxy Tab  Android Development] alroger:
It was already on!
[Galaxy Tab  Android Development] nhojeric214:
This is my problem
[Galaxy Tab  Android Development] Ichijoe:
Seem to me that the Partition Map on your Device is not compatible with the ROM your trying to install.

I'd ask you if you the ROM your trying to install was for your Device. But, I would assume that it was.

Basically what this "Message" is telling you that if you wish to continue to install that ROM. It will re-partition your Device, causing you to lose any sub-data (Photos etc... from your /Data Partition) from your Device if you continue to install it.

If that Data is important to you, you should first back it up....

Otherwise just re-run the update.zip again, to install your ROM.
[Galaxy Tab  Android Development] nhojeric214:
if you are referring to Data which is in the device storage (not the internal sdcard) then its fine with me as long as my tab comes back to life.

uhm can you please guide me to the steps i should follow if its not time consuming in your part? i feel so hopeless with this because i have no means of flashing roms thru odin since my usb connector isnt recognized with any computer i use anymore (i use mobilego in transfering downloaded roms to my tab) and that my only chance is the last rom zip i copied from my laptop before my tab went nuts. sorry for long post tho

PS i also formatted /system because i was updating the rom thru "dirty flashing" and now i cant boot to my previous rom.
[Galaxy Tab  Android Development] Ichijoe:
That's how I read it (The Error Message on your Phablet). If there is nothing on it.... That you care about. Then just re-run the Update.zip to confirm your wish to install it. At which point it will repartition, and reformat your Internal-SD (i.e. sdcard0), for reference sdcard1, is the Ext-SD or your MicroSD Card..... At least this is how it is on my P1000.

As long as the ROM is compatible with your P1000 x/x/x/x??? Then you have nothing to worry about. But any personal Files that may have been in /Data (Normally not touched when flashing ROMs), will be wiped from the Device. So if that doesn't bother you then all you have to do is to just re-run the updater once more. Which should hopefully ignore this "warning" and then install that ROM to your Device.

I can only guess that you must have an old Gingerbread (or older) Partition Map on your sdcard0 which is why your getting that error. Once your update this you should not be seeing this ever again.
[Galaxy Tab  Android Development] nhojeric214:
i ditched my GB years ago and in fact im on kitkat for a couple of months now since its stable release. this problem just happened in the recent updates of omni rom. btw i was able to flash resurrection remix and thought that my tab was already okay and proceeded in flashing omni rom (latest build) but same problem arose. idk whats the problem with omni rom on my tab.
[Galaxy Tab  Android Development] Ichijoe:
IIRC Resurrection = a Cyanogenmod 11 build, that installs CWM Recovery. Where OmniROM prefers TWERP.

When I switch from One or the other. It usually ends in a "Dead Android" (CWM Recovery) , screen. Until I reinstall it again, where it then reboots back into TWERP again. But, that this would have on the /Data Partition, I have frankly no idea? Perhaps you might consider installing a new *.pit File though Oden3. To try and bypass this Error.
[Galaxy Tab  Android Development] nhojeric214:
The problem is that my original charger was lost so i had to buy another one which is not original. At first my tab was still recognized on my laptop using the new connector but now it says usb device not recognized. To think it cost me around $15 for the new charger. So no chance of using odin again :(
[Galaxy Tab  Android Development] ulev:
I run into the same screen when I switched from CM11 to OMNI a few days ago. Tried rerunning update.zip several time as suggested to no avail. So I had to (partially) restock using ODIN to get the original recovery. From there the regular install of the OMNI ROM worked without a problem.

My guess is some unresolved issue connected to the new LVM partitions. For example an older version of Titanium Backup I am using seems to have LVM issues too.

As you cannot use ODIN via USB, why don't you use your microSD card and copy a late CM11 zipfile to it on your PC? I think you should be able to install it successfully through your remaining (intact) CWM and get back to a working system. From there you can reconsider you options to switch to OMNI without the pressure you have now...
[Galaxy Tab  Android Development] Ichijoe:
You might wish to have a peep on Fleebay... When I was given my P1000, as a gift last year. It too came without a proper USB and Charger. So I had little choice but to get another Original Charger + Cable. I think I only paid like 12.00~€'s for it. Searching it now I see a few for like 30€ overpriced! to more like 10.90€ (or $14.95USD). I also had a ~fake~ Cable. It works well enough as a Data Transfer Cable, I think it fails to feed the Device any power though :7... But, there it is.

Besides One word of warning about OmniROM... (Or at least this OmniROM...), this ROM does NOT support Mass USB Storage. Installing this will only give you MTP (Kies Mode), and PTP (Photo Transfer Mode). There are time when I personally need to have USB Storage. So I'm currently using the [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.2][P1/L/N][Kernel 3.0.x][2014-05-16]. Which I find seems to work fine for me plus it also has the older USB Mass Storage Mode.
[Galaxy Tab  Android Development] humberos:
Btw, all UMS patches are already uploaded... waiting review

http://migre.me/jg2A0
[Galaxy Tab  Android Development] humberos:
Hi guys!

Please let me know if you want to remove ro.config.low_ram property.

I think if we'll get positive feedbacks about this change then we can drop it.

Thanks!
[Galaxy Tab  Android Development] Ichijoe:
If by this you mean we can patch UMS back into this ROM then I for One welcome it!
[Galaxy Tab  Android Development] nhojeric214:
That's exactly what i am trying to do. Actually i was able to boot to resurrection remix rom (as I've stated earlier) and tried to flash omni rom but again the same error persist. I downloaded the latest omni rom update but still no luck. Too bad i really loved how smooth omni rom was :(
[Galaxy Tab  Android Development] nhojeric214:
Update: for some reasoin i was able to flash omni rom again. I think my tab cooperated with me this time ?. Anyway thanks a lot guys for helping me out with my problem and for your time ?
[Galaxy Tab  Android Development] ulev:
So how did you do it?

---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------

I changed the flag to "false" without any problems. So I would vote for dropping it...
[Galaxy Tab  Android Development] nhojeric214:
Well i really don't know how i did it. I just wiped and wiped and flashed resurrection remix rom. Then after i was able to flash it, i tried to flash omni and then viola im back ?

---------- Post added at 12:02 PM ---------- Previous post was at 11:58 AM ----------

Just one thing, how do i turn off this scary notification tone when i have notifications? Its kinda creepy when everything is silent especially when its midnight ?
[Galaxy Tab  Android Development] ohtoulouz:
Unknown baseband and IMEI

Hi,

I flashed 21/05 nightly directly over 07/05 nightly (different partition layouts) and loose baseband and IMEI. Flashing 07/05 back allows me to recover baseband and IMEI. What did I do wrong ? Is restocking using Overcome mandatory ?

Thanks

edit: Ooops! I flashed 21/04 nightly and not 21/05 !! Stupid...
[Galaxy Tab  Android Development] humberos:
Finally - 720p support

Finally - 720p video recording support

here go!

https://gerrit.omnirom.org/#/c/7669/

will be available at 20140523 nightly build.

Enjoy!
[Galaxy Tab  Android Development] ohtoulouz:
Hi,

Finally, I flashed CM11, then 22/05 nightly like it was suggested earlier. Everything went fine but data is 1,4 GB. I thought it was supposed to be 1,5... Did I miss something?

Thanks for your support !
[Galaxy Tab  Android Development] humberos:
Yup!

1.5GB is total space available but you may checked free space, right.
[Galaxy Tab  Android Development] ohtoulouz:
Thanks,

here is what I got (from 07/05 nightly -> flash CM11 22/05 nightly -> flash omni 22/05 nightly)

Any idea ?
[Galaxy Tab  Android Development] ulev:
Nothing wrong, same reading here. When I look at it in Titanium Backup it tells me 1.48GB... So probably they just cut off the last digit...
[Galaxy Tab  Android Development] ohtoulouz:
Thanks,

you're right, TB tells 1.50GB... Seems not to be a problem.
[Galaxy Tab  Android Development] Cleverfish:
i'm also got 1.4GB and in titanium backup it shows 1.48GB. direct flash from overcome to omni, and didn't had any problems, tab running faster than previous.

[MENTION=3031478]humberos[/MENTION], i have changed low ram config to false, as a result tab keeps rebooting.. maybe due to insufficient ram?

Sent from my GT-P1000
[Galaxy Tab  Android Development] aalvico:
Blur lockscreen doesn't work.... Also I don't see an option to add widgets on the lockscreen (usually I use dashclock) ...doesn't show camera widget if enable.... Any solution ?
[Galaxy Tab  Android Development] humberos:
My guess is YES. But I need logs for sure.

You can comment out this property instead setting a "false" value. Just a tip.

Sorry, some features isn't available for low-memory devices.

You can try these features by removing low ram config.
[Galaxy Tab  Android Development] aalvico:
Is possible transparent status bar on GEL and lockscreen ?
[Galaxy Tab  Android Development] ulev:
Use low memory -false- and "force high end graphics" and you got all transparency you want...

[MENTION=3031478]humberos[/MENTION]: I am on this ROM for a week now and I just love it. :good:

There are only two small things I would wish to change: (1) A good file manager directly in the ROM and (2) the usual AP on/off tile in the status bar/quick settings of CM. Can't even get the AP tile with the Xposed modules I tried.
[Galaxy Tab  Android Development] humberos:
We can use:

Settings --> Performance --> Advanced Settings -> Force high-end graphics.

... and get transparency effect.

(1): I will talk with Omni team.

(2): same (1)

Thanks.
[Galaxy Tab  Android Development] ulev:
Found some answers:

(1) An OMNI team member said some time ago a file manager is on their list, hence a low priority

(2) On the quick settings tiles I learned how innovative OMNI really is! Many of them can be flipped around swiping left or right over them. Amazingly the WIFI tile turn around becomes the Tethering tile. A great function many might have missed.
[Galaxy Tab  Android Development] aalvico:
Thanks...High end config works for transparency and I didn't notice any problem after enable it ...low ram didn't for blur lockscreen but open choose widget option... With it I can see all options on google camera (which video crashes after video update) but unfortunately probably as expected it freezes during photo sphere and got slow on panorama
[Galaxy Tab  Android Development] nhojeric214:
Got a random reboot while playing clash of clans on the latest build.
[Galaxy Tab  Android Development] humberos:
You'd need to get a logcat of the reboot.

Try checking Settings -> Applications -> Running and see if you're running too many services or not.
[Galaxy Tab  Android Development] Mjoelnir77:
Is the following part of the omni build for our tab or is it intended to be in the future?

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

And this https://github.com/JustArchi/android_build/commit/8e1b82c082a8de9160e6c0fc3ded37b591c3e517

I stumbled upon that when looking for a new ROM for my girlfriends P7500 and the last build including that seems indeed to be snappier then everything before. It also sounds quite reasonable.
[Galaxy Tab  Android Development] humberos:
Unfortunately I can't confirm if we will get these features on official builds.

I am getting a royal pain to get UMS patches merged....

I think may exists another fork of Omni or CM that will use these features.

I am sorry!
[Galaxy Tab  Android Development] white-energy:
I will be compiling some builds using JustArchi stuff and comeback with results and download links :)

Soon. :good:
[Galaxy Tab  Android Development] Ichijoe:
Hi I managed to use something called ROM Toolbox Lite to edit the /system/build.prop.

Oddly its the only thing that seems to work for me. Anyway I managed to flag the ro.config.low_ram from true, to false, and so have some Lockscreen Widgets working now thankfully. But, I'm wondering why I still don't have my Camera Widget installed even though its checked by default in the ROM? It was never there, and I see no way to actually add it there either.
[Galaxy Tab  Android Development] ulev:
Looking forward to the results. However, we shouldn't expect too much with the limited resources we have on the P-1000 in terms of RAM, /system and /data limitations. A possible gain in speed might simply cost us too much memory...
[Galaxy Tab  Android Development] jebll:
P1 -how to get original samsung keyboard dock to function?

Great rom, easy install coming from overcome.

Thanks
[Galaxy Tab  Android Development] leleobhz:
How i can restock it? I tried to find a valid original firmware but samfirm site give me a 404 and i dont know how to do now.

Im using the storm firmware and i want to try the omni here.

Thanks!
[Galaxy Tab  Android Development] Ichijoe:
I'd like to take the time to post yet another possible bug...

This time its to do with the Headset (Call + End / Hold -- Play / Pause Button)....

So I've finally found some reportedly Stock White Hard Plastic Headphones for my GT-P1000

These Phones do in fact work in the exact way as the Stock Phones on my Galaxy S (GT-I9000) DON'T!...

On a Samsung Stock ROM these "Pictured" Phones just work, I can take, and end Calls with the push of the Button, ditto with the Play & Pause for my Music Player. Sadly however in the most current OmniROM P1 Build the Button doesn't do jack. But at least the Stereo is working where-as it wasn't for my GT-I9000 Headset. So FYI Galaxy S Headsets would seem to be incompatible for the GT-P1000.

So could someone look into this? I mean am I the only One who uses this as a Phablet?

I'm less pressed about phoning as I'm more of a data person then One who hangs on the Phone, but it would be nice to tackle that chore when needed.

Thanks for looking at this!
[Galaxy Tab  Android Development] boatpoyo:
It's here : https://docs.google.com/file/d/0BzJut_BZm8NTUjc1OVl6VzRsa0U/preview
[Galaxy Tab  Android Development] humberos:
Android 4.4.3

Android 4.4.3

Let's move on!

https://plus.google.com/110828004175243490149/posts/6Pz9fxPTbC1
[Galaxy Tab  Android Development] rpzk:
Hi folks! I am having a charging problem. The tab charges well in 220v but in a 110v it charges very slowly and only with screen off!
[Galaxy Tab  Android Development] priyana:
Only in this ROM?
[Galaxy Tab  Android Development] Ichijoe:
1) Its only been out for about Three Days now.

2) Your Link is broken.

OmniROM is perhaps One of the best ROMs out now, I'd not go as far to call it perfect. ITS NOT. But, I'm fairly sure someone is looking at 4.4.3 at the moment. But, it'll likely still be a short while before we see anything. So chillax!
[Galaxy Tab  Android Development] alessandronip:
The same happens to me with the samsung charger.

With the previous ROM (CM 10.1) worked.
[Galaxy Tab  Android Development] rpzk:
Only with omnirom! In CM11 and before it works fine!
[Galaxy Tab  Android Development] white-energy:
Can we please have the first post organized? with clean pictures and thumbnails (clickable to zoom) instead of huge pictures? can a mod or OP do something about that??? organized text too... keep it simple and short.
[Galaxy Tab  Android Development] humberos:
btw, the link ins't broken! You need a Google+ account.

and yes... we have someone looking at 4.4.3 at the moment...

https://plus.google.com/110828004175243490149/posts/6Pz9fxPTbC1
[Galaxy Tab  Android Development] humberos:
I will check it, thanks!

Edited:

Sorry! I can't reproduce this issue.

I've tested it here and it is charging normally.

If you can, send me kernel logs.

Just open terminal app and type:

$ su

# cat /proc/kmsg > /sdcard/kmsg.log

Plug and unplug the tab charger.

Thanks!
[Galaxy Tab  Android Development] rpzk:
Excuse me sir, but i could not reproduce it within last build!

It seems to be working properly now!

Thanks for your concern!

My Tab is a P1000L!
[Galaxy Tab  Android Development] leleobhz:
Issues:

* On P1000N, like storm31 rom, calls have a VERY VERY VERY low volume. Speaker have low volume but in earphones - even using good earphones like Philips for Cellphones - is impossible to listen if the environment isnt quiet. In storm31 ROM i've tested Voodoo Sound with sucess for music, but no effect for calls.

* No USB Mass Storage?

Probably Android/Linux issue:

* MTP only works if connected with screen unlocked. Also, once MTP crashes, it takes a lot of reconnects to recognize in Ubuntu (1.1.6-20-g1b9f164-1ubuntu2 of libmtp).
[Galaxy Tab  Android Development] salahmed:
done some cleaning to the OP... some text in downloads section can not be removed, it has some vital info about previous builds that contain different layouts. in case any one want to try them.
[Galaxy Tab  Android Development] white-energy:
That's grreat! I'm seeing some cosmetic progress already :highfive:
[Galaxy Tab  Android Development] humberos:
Sorry, can't reproduce this issue on my P1000L (same kernel).

Logs are welcome.

I think that you didn't read all posts before this (on this thread) about USB conn.

MTP works fine (actually is not fine as well I know), but UMS definately is better than MTP.

But Omni core team isn't agree and you can send a ticket to them.

Thanks!
[Galaxy Tab  Android Development] leleobhz:
What kind of logging is best for you? I think its usefull collect it just before a call starts but i dont know what i must to send to you.

And the modem.bin affects this kind of thing? Its a way try to change modem.bin and if its a good idea, witch one i must use?

Thanks.
[Galaxy Tab  Android Development] humberos:
Using: Terminal App or ADB

* During first call

$ su
# cat /proc/kmsg > /sdcard/kmsg.log

* During second call

$ su
# logcat > /sdcard/logcat.log

You can change modem.bin using adb (as root user) or by some file manager app (with su permissions).

* Be careful with permissions setup.

I didn't see any difference,... some users related something about power consumption but it was not confirmed yet.

You can post all logs here (at XDA) or here http://paste.omnirom.org/ .

Thanks!
[Galaxy Tab  Android Development] leleobhz:
1) Changed modem (Perms ok, etc). to JPZ P1000N from you in the fixed topic in this subforim.

2) Reboot

3)

leonardo  ewok  ~  Documentos  Tablet  $ pastebinit FirstCall.txt

http://paste.ubuntu.com/7597785/

leonardo  ewok  ~  Documentos  Tablet  $ pastebinit SecondCall.txt

http://paste.ubuntu.com/7597786/

FirstCall.txt command: adb shell "su -c \"cat /proc/kmsg\"" > FirstCall.txt

SecondCall.txt command: adb shell "su -c \"logcat\"" > SecondCall.txt

Both calls i started log before start the call, started the call, turned off the call and stopped the log. In FirstCall i tried to raise the volume up until max (And before volume adjust, it was at the high level).
[Galaxy Tab  Android Development] humberos:
I saw that you are using a headset plugged. Is it working fine on another device?

Edited:

<4>[ 422.981179] 4 pole headset attached : adc = 1965
[Galaxy Tab  Android Development] alessandronip:
I have a Google+ account, but the link is still broken.

---------- Post added at 08:17 AM ---------- Previous post was at 07:26 AM ----------

I confirm, with 2014/06/03 build work fine.

-edit-

Good news, 4.4.3 build is out.

It can be installed directly? Must be updated gapps.
[Galaxy Tab  Android Development] boatpoyo:
Yes, it can. Don't have to update gapps.
[Galaxy Tab  Android Development] salahmed:
Minor update to the OP. Thank you [MENTION=3031478]humberos[/MENTION]

Clean install 6 June 4.4.3 with the new Gapps. Everything seems to be working fine and fast as usual.
[Galaxy Tab  Android Development] humberos:
Tvout is broken.

I am working on.

Thanks!

------------------------------------------------

NVM, may I should check my local skia repo once again.
[Galaxy Tab  Android Development] Ichijoe:
I have finally managed to get a pair of Stock? Headsets for my P1000 (Int'l GSM a.k.a "P1"), with the current JPZ? Modem (as per what this ROM defaults to. The Button doesn't do diddly! I've tested this against both Samsung Stock (Gingerbread 2.3.3), and the CM-11 SGT7 ROM, both of which are working to degrees. That is CM-11 SGT7 will not drop (i.e. Hang up the Phone), and instead only mutes the Mic. Not that these Bugs should be reported here. For obvious reasons...
[Galaxy Tab  Android Development] humberos:
I will check sec_jack driver for P1 headset.

Btw, you're right when you said about differences between Aries and P1.
[Galaxy Tab  Android Development] Arch9:
where can i download the new cwm recovery to flash this rom? i'm still having old cwm 3