yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] safety1st:
Just one question, how are you guys gonna tackle the extinction of Dalvik, now that it has been totally wiped out by ART in the main code branch?

http://www.androidauthority.com/art-replaces-dalvik-aosp-394904/
[Galaxy Tab  Android Development] metterschling:
Looks like real-word 4.4.4 ROMs still come with Dalvik: http://xdaforums.com/showthread.php?p=53540928

Xprivacy is an Xposed module & Xposed requires Dalvik...
[Galaxy Tab  Android Development] nnay:
Hello everybody,

I need some help because I didn't flash anything on my tab for a very long time... So for what I have understand, I have to restock the tab with the GB-Stock-safe-v5 file with Odin. My question is : after that, with the recovery installed, does I will be able to flash the rom + gapps + supersu through the recovery?
[Galaxy Tab  Android Development] priyana:
With overcome kernel, yes.

It has cwm 5.

I just did that not long ago.

Edit: but you need to flash the rom twice.

First time only "upgrades" your recovery to twrp.
[Galaxy Tab  Android Development] safety1st:
Downloading Omni Rom build 4.4.4 20140622.... Feedback later.....

Gonna try ART right away

Kudos to all Omni Team and to [MENTION=3031478]humberos[/MENTION]
[Galaxy Tab  Android Development] safety1st:
Still on test mode
[Galaxy Tab  Android Development] safety1st:
This build is still on "DALVIK"
[Galaxy Tab  Android Development] alessandronip:
4.4.4

Thanks, it works well.

Only a small mistake, really trivial, the audio output is directed to the TV cable although the TV output configuration is disabled.

Keep this in mind if you happen to revise this part.

Great, now I work for everything, even the error in sending emails that I had already reported.
[Galaxy Tab  Android Development] humberos:
The audio routing works from 30pin cable events, I mean from kernel space.

The Tvout service works on userspace.

Nice to know that your reported issues are fixed!
[Galaxy Tab  Android Development] leleobhz:
But still low volume in call's using headphones :(

Also, i cant remember if i asked before but there is a "best" modem for Brazil carriers? Which one you're using, [MENTION=3031478]humberos[/MENTION] ?

Also modem between L and N variants are compatible?
[Galaxy Tab  Android Development] aalvico:
Is there a limitation to use 30 minutes display on before sleep ? It doesn't show the option in English and shows but crash in other languages... Works in my nexus with omni... Not a huge problem, more to know why.
[Galaxy Tab  Android Development] humberos:
Sincerely I can't reproduce this behaviour.

I don't know where is the problem even by checking your logs.

I am really sorry!

I never have tested these modems... some users claimed something about power consumption improvement but I don't have numbers to prove that.

At least I think all P1 (gsm variants) modems are compatible.
[Galaxy Tab  Android Development] humberos:
Please, could you open a JIRA ticket?

http://jira.omnirom.org

Thank you!
[Galaxy Tab  Android Development] safety1st:
Increasing of Performance

Looks like next build will bring more performance i guess :confused: http://omni.cmxlog.com/4.4/p1/

zram increases performance by avoiding paging to disk and using a compressed block device in RAM instead, :good:

Can't wait to test this enhancement to our old device :D
[Galaxy Tab  Android Development] humberos:
yep!

I hope that you enjoy it!
[Galaxy Tab  Android Development] safety1st:
Random disconnection while Tethering or hotspot active

[MENTION=3031478]humberos[/MENTION] can you please check the issue on tethering, i experienced random disconnection

https://s3.amazonaws.com/pushbullet...6Roju78X12FgpdCM6/Log_2014-06-28_11-52-09.txt

https://s3.amazonaws.com/pushbullet...lb1bCHsFDrVkFXBwN/Log_2014-06-28_11-52-11.txt
[Galaxy Tab  Android Development] alessandronip:
I confirm that, to me it does not work.

Tested on two different PCs and two OS (WinXP and Windows 7) behaves the same way, if I give the command Mount disks are not seen even if I do not have USB errors.

Where are the log of TWRP?
[Galaxy Tab  Android Development] humberos:
You can extract that log from:

/tmp/recovery.log
[Galaxy Tab  Android Development] alessandronip:
This is my test:

-Reboot into recovery and connect to PC.

In device manager there are two "Linux File-CD" devices. (NoMount.png)

-Mount

The two "Linux File-CD" peripheral disappear. (Mount.png)

Bye. Paolo.
[Galaxy Tab  Android Development] safety1st:
Massive updating and staging... More patches

Can't wait for the next build to test :fingers-crossed: it will be more responsive and fluid... just a quick experience tip try to fully restock before flashing this new build to feel it's difference from other build.

http://omni.cmxlog.com/4.4/p1/

[MENTION=3031478]humberos[/MENTION] i'll gonna try to pull the logcat on some glitches on 20140629 build. :confused:
[Galaxy Tab  Android Development] leleobhz:
Restock is really necessary? What justifies this procedure?
[Galaxy Tab  Android Development] safety1st:
[MENTION=1624729]leleobhz[/MENTION] it's not substantial as i posted "as what i've experienced" ;)

for the record the reason why i used to do clean installation is because i don't get the full size of my internal memory when doing the dirty flashing
[Galaxy Tab  Android Development] safety1st:
Devices freezes on Samsung Logo on latest build (20140704)

I upgrade my device on the latest nightly which is 0704, installation/update was successful, but device failed to boot (device freezes on samsung logo) i tried to restock and do clean installation but same result, device only show Samsung logo for a long time, that's why i revert back to 0629 build. :confused: Any hint [MENTION=3031478]humberos[/MENTION]?

Thanks
[Galaxy Tab  Android Development] humberos:
Yes! I saw!

For some reason the kernel wasn't flashed during installation process.

So, it requires heimdall to manually get kernel installed.

Very weird behaviour... We need to check the reason....:confused:

I am very busy at moment but I will take a look when I get free time.
[Galaxy Tab  Android Development] safety1st:
Ok thanks, or maybe I will just wait for the next build ?
[Galaxy Tab  Android Development] humberos:
I found the problem:

I:injecttwrp --dump /tmp/backup_recovery_ramdisk.img /tmp/injected_boot.img --flash process ended with ERROR=1

https://github.com/omnirom/android_...on/blob/android-4.4/BoardConfigCommon.mk#L136

I will check this flag and fix it.
[Galaxy Tab  Android Development] safety1st:
Take your time dude.... Just enjoy the weekend
[Galaxy Tab  Android Development] Ichijoe:
Which Kernel? What Kernel AFAIK the TWERP Kernel for the P1 doesn't exist as a standalone.

*EDIT* Six that....

It seems the "Recovery Method" has been described back on page One, of this Thread.

My advice is to download the Heimdall One-Click Recovery... (For the USB Drivers!), and the current buggy ROM from the OmniROM Site. Use WinRAR (Or whatever...), to extract the boot.img for the P1000 (Int'l GSM) .... Or boot_p1ln.img for those with an "L" or "N" Tab.

Then follow the directions at the beginning of this Thread, to install.

I'm just thankful I didn't have to whip everything just to recover from this.
[Galaxy Tab  Android Development] alessandronip:
Extract boot.bin from .zip.

I used build 0703.
[Galaxy Tab  Android Development] safety1st:
[MENTION=4430830]alessandronip[/MENTION] you're using 0703 build from update from 0629 right? because when i try to install build 0703 ( a clean installation/restock for i came from glitch when i install 0704 build) same result like 0704 build, freezes upon installation on Samsung logo :confused:
[Galaxy Tab  Android Development] alessandronip:
I manually updated from 0625 to 0703 without any problems.

The 0629 did not work well.
[Galaxy Tab  Android Development] safety1st:
Thanks for the info...:) appreciated a lot
[Galaxy Tab  Android Development] humberos:
I got it fixed: https://gerrit.omnirom.org/8431

Just waiting reviewers and then next build.
[Galaxy Tab  Android Development] truevision:
Great rom !

There is a way to set a "completely black" ?
[Galaxy Tab  Android Development] chickoo.t90:
Will the 05/07 nightly have the platform issue fixed ?
[Galaxy Tab  Android Development] Ichijoe:
It seems there was a "problem" with the Kernel install in the 20140703 Auto Update?

Of this I too can confirm, and I already had in this Thread. Sadly it seems that the Update that got pushed again this morning.

My time (i.e. 20140704), is still just as buggy.

That is I had to force install the boot.img (for the P1000 int'l GSM) onto my Phablet though Heimdall again.

Is this gonna be a new thing now unless I wipe and start a clean install with the most current version. Or can this still be fixed?

I see that on the DL site their is an update to 20140705. The Auto Update of course seems blind to it again... I'll download it, and install it manually and report back again.

EDIT: It seems that the 20140705 was in fact the same (or compiled on), 20140704, as was the Auto Update. In any case even as a Manual Install, I still had to install the Kernel separately though.
[Galaxy Tab  Android Development] salahmed:
Just wait for the next build. It should be fixed by humberos
[Galaxy Tab  Android Development] safety1st:
Currently on the latest build 0706 (no missing platform) ;)
[Galaxy Tab  Android Development] humberos:
The fix isn't merged yet.

https://gerrit.omnirom.org/#/c/8431/
[Galaxy Tab  Android Development] safety1st:
It's maybe because i came from an update i guess? So i didn't encounter the same problem before
[Galaxy Tab  Android Development] safety1st:
InCallUI: non intrusive incall ui rework not Working

Latest build InCallUI: non intrusive incall ui rework is not working :confused:
[Galaxy Tab  Android Development] Ichijoe:
Its been been Three Days, and as many Updates now, and the Kernel is still not working after these "Updates", and must be installed manually through Heimdall. I dare say whats going on?
[Galaxy Tab  Android Development] Ukitaki:
now everything is okey! i`m running on 07.07.14 build!
[Galaxy Tab  Android Development] safety1st:
Nope, not fixed yet :( you will not encounter any problem if you flash the update on the build later than 20140629 and below. But if update from build 0703 to present installation will stuck. Missing platform is still not merge on this build i guess am i right [MENTION=3031478]humberos[/MENTION] :confused: (for i encounter the same issue and problem again.

http://omni.cmxlog.com/4.4/p1/ fix will be on the next build
[Galaxy Tab  Android Development] humberos:
The patch was merged.

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

@all

FYI

It's not a P1 kernel issue.

Just a twrp patch for mtdutils changes with wrong filter.

Please, wait next build.

Let's move on!
[Galaxy Tab  Android Development] white-energy:
Guys, i've been prompted to flash an update of 7th of July, i agreed to flash it, the flashing process went correctly and now it doesn't boot! it's stuck at the Galaxy TAB Samsung bootscreen.. i can't get passed it nor i can get into recovery mode, only thing i could do is Download mode access.. What happened?

P.S: Galaxy TAB P1 GSM

EDIT: Fixed it using Heimdall by uploading the boot.img on download mode extracted from the update zip :)
[Galaxy Tab  Android Development] Ichijoe:
The same thing that has happened to me for the last Four (or was it Five Days?) now.

For some reason the Kernel is failing to install properly, in these latest updates.

All is not however lost, you'll probably need to download, and install Heimdalls "One Click Recovery". (i.e. For the Triangle Soft-brick).

Not because the Update bricked the Phablet. (Well that's a different debate...), but so you can get the proper USB Drivers for the P1/N/L installed on your PC side of things.... Once the Drivers are installed you can then close the "One Click Recovery" as we wont be needing it anymore.

Once you have the Drivers from the One Click Recovery installed you just need to run the Heimdall Suite (See the very first Post!)....

Place your Phablet into Download Mode, and start the "Heimdall-frontend.exe" then

Step One "Utilities" -> "Detect Device" -> "Detect". (This is why you kinda need to deal with the "One Click Recovery" first.) The "Output" Field should say "Device Detected"

Step Two... Click on "Save As..." then just use a Filename like "p1" or "p1l" or "p1n" depending on your Device.

Step Three... "Download" (Your Pit File to your Save as Location)

Now switch to the "Flash" Tab.

Step One "Browse" this should be the same Directory where you saved your Pit File to.

Step Two click "Add"

Step Three (Its a scroller) choose "Kernel"

Step Four. Depends upon which Device you have beit the "p1" (boot.img), "or the "L" and, "N" (boot_p1ln.img), versions of the Device.

You'll find these inside any of the ROMs you'll have to manually download these from http://dl.omnirom.org/p1/ and extract such File(s) as you need with either WinRAR, (or 7Zip?)... In any case its this particular File that needs to be linked there.

Step Six... Click Start....

Now depending on if you follow Step Five, or NOT! (From the First Post), the Device will then reboot automatically, and it will be working again as normal.... If it doesn't reboot... Then just force reset it by holding the Power Button till it does reboot.

Simples.... I do hope that this can be fixed soon though...
[Galaxy Tab  Android Development] truevision:
Heimdall is only for Windows ? On Linux there is a solution ?!
[Galaxy Tab  Android Development] priyana:
Heimdal is in Linux and Mac too. You may want to learn the command line. There is a front end I think. But I never bother to install that.
[Galaxy Tab  Android Development] truevision:
I'm looking Heimdal now, I saw is "cross-platform" (Linux yet) ;)

thanx !
[Galaxy Tab  Android Development] aalvico:
Boot problem not fixed yet on jul 10 update :/.

Edit: solved, so the problem was not on the 0710 file but something before that, that only appeared after update.
[Galaxy Tab  Android Development] humberos:
It is.

Make sure that you aren't using a recovery with mtd filter problem.

If you did flash the kernel with broken recovery manually then it won't flash any kernel image anymore (due to mtd handler is broken).

You should to flash the latest kernel before, then flash latest ROM and let me know.

Thanks.
[Galaxy Tab  Android Development] aalvico:
I was on 0622 and updated to 0710 then got the problem for the first time.
[Galaxy Tab  Android Development] humberos:
Hummm!!

Weird,.... although the broken patch was merged since June 30th but the fix came at July 7th.

Broken

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

Fixed

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

if you have the kernel built between these days then your recovery is broken.

Please, could you send me logs?

/sdcard/bml_over_mtd.log

Thanks.
[Galaxy Tab  Android Development] ohtoulouz:
Hi,

I don't know if it helps: I dirty flashed 10/07 nightly over 26/06 nightly and instal went fine.

Cheers and thank you [MENTION=3031478]humberos[/MENTION] for keeping our old tab up to date !
[Galaxy Tab  Android Development] Ichijoe:
It might be worth noting... Well I found myself guilty of doing this... But, when you go to flash either the "boot.img" or "boot_p1ln.img", it may help if you try to use the most current version available. instead of the broken?! July 4th One.. That I continuously found myself using. Because I didn't care to keep downloading a near 200MB download just to get the 7kb Kernel File.[/i]

If this makes a difference I haven't tested it out yet somehow I failed to properly seat my Phablet last night and woke up to find a dead Phablet. T_T.

So I'll check for updates in a bit, once I get it charged back up, and see how it goes.

**EDIT**

Ok so I managed to get it charged up about 50-ish percent, and did an update check. Having tossed the seemingly broken July 4th Kernel for something newer... July 9th's (I think...) I was finally able to complete the Update process. (i.e. Without having to separately having to fire up Heimdall to flash the Kernel), for the first time in over a Week!

My advice to those still flashing the Kernel though Heimdall would be to find a newer Kernel from the 9th, or 10th (i.e. Yesterday or Today's Kernel), from the temporal moment in which I'm writing this now.

YMMV.... But, for me, this seems to have fixed this rather annoying bug.
[Galaxy Tab  Android Development] kristalic:
humberos,

Hi,

At the last firmware (including 10.07.14) TAB when connected to USB a charger not inscription "Charging" and when the charge already reached 99% not writes disconnect the charger. On the firmware from xx.06.14 is not noticed the such bug,fix plz if possible.

And I think the power consumption increased
[Galaxy Tab  Android Development] Ichijoe:
I've just managed to fully complete an auto update, after replacing what I had judged to be an outdated Kernel (At the time it was the 10 of July, and the Kernel was dated the 9th.) So I tossed it and, decided to use that One instead. This seems to have fixed that Kernel Bug that everyones been getting hit with for these last few days.

As to the "Charging xx%" or the on the "Connect your charger." messages they are appearing on my P1 at the moment.

OmniROM: 4.4.4-20140710

Kernel: July 10 12:28:45 CEST 2014

Though there seems to be very considerable lag if I remove the Charger. The message will continue to say "Charging xx%", even long after I remove it. Re-inserting the Charger again will change the message to "Please connect your charger."...

I would also add that I also use ROM Toolbox Lite to set the "low ram" (in build.prop) from "true" to "false" on as well. So I'm currently trying to set it back to see if the same messages appear in low ram "true" mode as well....

Having done this... I can say with some confidence that I'm experiencing the same kinda "lag" on my P1 between such messages on my lock screen. Beit low ram "true" or "false. It may also be worth pointing out that I'm also using the Google Now Launcher. FWIW. But, I'm gonna be resetting my P1 back into Low Ram = false mode again now.
[Galaxy Tab  Android Development] kristalic:
I have the same kernel, updated to this kernel using Heimdall but now she firmware downloaded of wifi and put without problems.

View attachment 2845531

It looks like when connected to a charger USB

View attachment 2845554
[Galaxy Tab  Android Development] aalvico:
Now it updated from 0710 to 0711 without boot problems ... Good, but nothing to see on my log file anymore...anyway thanks
[Galaxy Tab  Android Development] RogerG:
OTA update from 0630 to 0711 worked without any problem - thanks for all the excellent work :good:

let me just say how INCREDIBLE it is to have the most recent roms running on hardware that is almost 4 years old - and which hasn't seen any official love for 2.5 years. we're on 4.4.4 (maybe soon 5?), when we "should" be on 2.3.6.

humberos - you (and all the other devs!) really rock :victory:

two minor questions:

.) is there a way to add a "lock" tile to the quick settings (to quickly turn device-locking on/off)? I used that a lot under CM11...

.) does usb-host work on omni? I had it working on the tab a long time ago (ICS?) but couldn't get it to work just now. HW-wise I use the correct setup with a splitter cable, adapter and ext. power source, SW-wise I use sztupy's usb host controller - which DOES recognize the attached usb-flash drive and gives me no errors when trying to mount it, but when I try to access the path with a file explorer, the folder is always empty. (folder is read/write; have tried fat & fat32 flashdrives - both are recognized but seem not to get mounted?)

thanks for any hints!
[Galaxy Tab  Android Development] evo3:
I tried to upgrade my P1000 from 0703 to 0711 and I have now the same boot problems already reported, the tab does not boot.

I read that it is possible to solved it by flashing the boot.img with heimdall, but I have a more serious problem because after installing the 0703 the charging port stopped working.

The symptoms are the tab is no more recognized by the PC and doesn't charge connected to power, it really charges if I turn off the screen and wifi or shutdown the tablet completly, but it charges very slowly takes all night to have a full charge.

I think some connections on the charging port are damaged.

I can put it in download mode

I can not put it into recovery mode

Is there anything I can do?

Thanks for your support.
[Galaxy Tab  Android Development] priyana:
Since you can still have it fully charged and put in download mode, you should not have problem to flash the kernel with heimdall.
[Galaxy Tab  Android Development] evo3:
Thanks pryana.

This was the first night that I put charging after upgrading to 0711 and didn't charge.

Anyway the tablet was no longer recognized by the PC and therefore couldn't use heimdall to flash boot.img, if there is no other way to do it I'll have to replace the charging port or is the end for my tab.
[Galaxy Tab  Android Development] safety1st:
If so try to restock your tab using Odin, flash GB Stock Safe5, then Overcome Kernel then flash the latest build of Omni Rom :cowboy:
[Galaxy Tab  Android Development] evo3:
I also can not use Odin because the PC does not recognize the tablet.

Thanks anyway.
[Galaxy Tab  Android Development] alroger:
Flashing kernel

Look, the PC doesn't have to recognize the tablet for you to flash the kernel.

Just put it in download mode and use heimdall in command line mode to flash it.

What might help, that helped me the other day, is this:

Plug it in the PC FIRST, then hold Power + VolDown till you get the Download Mode Screen on the Tab, then Run the the

heimdall flash --KERNEL boot.img --RECOVERY boot.img

Other tips: Use a good USB port, don't use USB HUBs, use original Tab cable.

PS: Remove SIM card and external SDcards.
[Galaxy Tab  Android Development] evo3:
I appreciate your help.

Previously I used your roms and they were amazing :good:.

At the moment I'm not able to boot into download mode, but as soon as possible I try to follow your instructions.

Thanks for all.
[Galaxy Tab  Android Development] alroger:
Even if you don't see anything on the screen, try charging it a bit on the AC adapter. Then Power+VolDown for at least 14 seconds... and heimdall on the command line... even if the screen is blank try it a few times.

PS: remove your SIM card and any external SDcards.
[Galaxy Tab  Android Development] leleobhz:
I did passed trough this trouble of boot. Heimdal --KERNEL using boot_p1ln.img fixed the issue for my P1000n.

But something messed up my SDCard and it now i got this in any Linux Kernel i try to use it:

[ 3624.523783] sd 41:0:0:0: [sdc] Assuming drive cache: write through

[ 3624.534748] sdc: sdc1

[ 3624.534759] sdc: p1 size 62326784 extends beyond EOD, enabling native capacity
[Galaxy Tab  Android Development] evo3:
Last night I followed your instructions:

Remove the sim card and external sd card.

Put into download mode and use heimdall in command line.

Connect the tablet to the PC with original cable. I have this error "USB device not recognized" as you could see on the image attached (it's in portuguese), I think the charging/dock port is damaged.

I did execute the heimdall code in command line several times, didn't work because heimdall couldn't detect the device and the code fails.

Then I try to plug and unplug the cable and force down and up the cable connection to the tablet many times and at same time execute the code.

In one of this tries the device could be detected for both PC and heimdall and did execute the code but with errors.

I don't have all the log, but it seems that flash kernel 100% but failed flashing recovery.

I tried to do it a several times more but the code always fails to complete.

Now i'm with this screen imageattached. I read in another post that is another download mode.

If it's true, I need have again the tablet recognized by PC and try to restock or flash boot.ini with heimdall it's not easy.

Thanks