yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] obsolete1:
Thanks for this, I just got DynaSysBars running (and WiFi back). Will see about adding this, thanks again.

Going to run over night (I work the LATE night shift) see if there are any issues. It will be available around 8am EST tomorrow if everything works.
[Moto G 4G Android Development] Polloos:
Thanks a lot for your work! :)
[Moto G 4G Android Development] JimYoung:
I'm anxious for testing the famous DSB :cool:
[Moto G 4G Android Development] hacktrix2006:
I will not be able to test this rom further as i have now gone back to stock ready for the Android 5.0 Lollipop. Which also means i am now classed as a naught boy due to having ART enabled and Device Encryption. sorry OP.
[Moto G 4G Android Development] obsolete1:
Its a little choppy at first but it works well enough. It does seem to eat the battery up pretty well. A "normal" usage night for me is a 15-20% percent drop in battery. With DSB enabled I nearly dropped 45%. Maybe I need to get into kernel development see if I can't make the kernel a little more efficient...

Uploading working build now, not too much longer.

**UPDATE

New build with Dynamic System Bars is available for download.

Added "Extras" section to OP for added features.

Thanks again folks.
[Moto G 4G Android Development] stefanthehuman:
No thank YOU sir!

With the recent progress is there hope for the OTA updates to come to life?:fingers-crossed:
[Moto G 4G Android Development] zackwire:
what a build! thanks [MENTION=5053748]obsolete1[/MENTION]...dsb looks awesome! way better than xposed modules i've been using. keep up the good work!
[Moto G 4G Android Development] Breezyz:
I have try the last build, dsb works great, some lags but i'ts awesome ;)
[Moto G 4G Android Development] rodsayd:
Don't forget to update the title of the post!
[Moto G 4G Android Development] obsolete1:
Fixed thanks.

Fancy new recents are in and working.

Working on impementing OTA next...all of this right before Lollipop better late then never I guess.
[Moto G 4G Android Development] Kahroo:
Do I need to install PA GAPPS? Or can I install the GAPPS for CM?
[Moto G 4G Android Development] obsolete1:
either or. it does not really matter
[Moto G 4G Android Development] obsolete1:
Main thread updated with an OTA, with the new tabbed recent enabled

PA OTA app is not functioning yet working on it though :good:
[Moto G 4G Android Development] zackwire:
Tabbed recents works like a charm for me, but DSB seems broken. Tried turning it OFF and ON, restarting, sguting the device off and on again, cleaning cache and dalvik, and nothing happened.
[Moto G 4G Android Development] obsolete1:
I'll get another build out later today...seems when I merged in the tabbed recents it cleared/moved something. I'll get it sorted out, thanks for the heads up.
[Moto G 4G Android Development] stefanthehuman:
Yay new build, not via OTA right ;)
[Moto G 4G Android Development] Kahroo:
Ok so I am coming from stock, can I flash the October 28th build or do I need to flash the 27th one first?
[Moto G 4G Android Development] JimYoung:
Yes, you can. It's not necessary to flash 10/27 build first.
[Moto G 4G Android Development] Breezyz:
It seems that dsb doesn't work on the last build

Edit: sorry I didn't read. I'll wait for the next release :)
[Moto G 4G Android Development] JimYoung:
New build is coming, read please: http://xdaforums.com/showthread.php?p=56357673
[Moto G 4G Android Development] obsolete1:
Something has gone atypical...more than likely no new build today.

Sorry for the delay
[Moto G 4G Android Development] stefanthehuman:
This thread is lonely today :(
[Moto G 4G Android Development] zackwire:
Another thing I've noticed, sometimes the system ui crashes and after a reboot the wallpaper goes back to the rom's original.

Enviado de meu XT1040 usando Tapatalk
[Moto G 4G Android Development] shokmah:
Flashed Oct 28th build since friday.also can confirm few system UI crash, mainly when using pie control in full immersive mode

however, everything else works as expected
[Moto G 4G Android Development] zackwire:
anyone know how to disable the rop right "clear all"button on recents tab? with the nav bar recents button doing the same function, the top button seems redundant.
[Moto G 4G Android Development] rodsayd:
Oct 28th build works without problems for daily usage?
[Moto G 4G Android Development] obsolete1:
Its what I've been running up until yesterday...I've gone back to stock for now.
[Moto G 4G Android Development] rodsayd:
I've just installed it, I will try it a few days. Until now is really fast :)

Edit: Until now the best ROM I've tried. No low ram bug, no crashes, everything works perfect! Thanks.
[Moto G 4G Android Development] obsolete1:
Long time no post...project not dead Lollipop is being worked on.

1st successful Alpha build completed this morning still checking things out. :victory:
[Moto G 4G Android Development] rodsayd:
Great news! This was the best KK ROM for me :)
[Nexus 5 Q&A, Help & Troubleshooting] Syrian Sniper:
Hello guys,

I want to install TouchControl on my Stock Android ROM (internal Rom) and install multirom.

is it possible ?

I started by flashing the kexec kernel then I let the Touchcontrol modify it , after than T-C worked perfectly but multirom stoped.

what should I do ?
[Nexus 5 Q&A, Help & Troubleshooting] Elluel:
TouchControl is deprecated.
[Nexus 5 Q&A, Help & Troubleshooting] Syrian Sniper:
Any other solution to enable s2w & multirom?
[Samsung Galaxy S II Plus] BECKHAM 7:
[MENTION=4692592]andrewww57[/MENTION] PLS I Need This Stock Update Pre-Rooted Odexed Rom
[Samsung Galaxy S II Plus] andixlm:
Now I can work with it and I'll make it within next few days.
[Samsung Galaxy S II Plus] BECKHAM 7:
THX Man Wish It Will Be Whitout Bugs Like The Older One You Have Done !!!
[Shield Tablet Android Development] Unjustified Dev:
I am not responsible for anything that happens while installing this recovery

Installation:

Download the attached recovery.img. You must have your bootloader unlocked before following this guide please refer HERE . You do not have to root your device to complete this installation.

To permanently flash to recovery partition

fastboot flash recovery recovery.img

To test the recovery image use

fastboot boot recovery.img

To install SuperSu/Root your device use the flashable zip from Chainfire's thread. No direct links let's give him credits

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

Current issues:

It appears to be rotated 180 degrees the wrong way. It's rotated that way due to the framebuffer. Don't worry it does not effect the performance in any way.

Source:

device https://github.com/C457/android_device_nvidia_wx_na_wf

kernel https://github.com/C457/android_kernel_nvidia_ardbeg

If you want to build the recovery to fix the 180 degree rotated issue you will need one patch from google

http://gerrit.vanir.co:8080/#/c/324/

Thanks

Huge thanks to [MENTION=3710905]Keithn[/MENTION] for testing all my bad images

If you would like to help me purchase this tablet follow the link below

http://www.gofundme.com/dbb08k
[Shield Tablet Android Development] Unjustified Dev:
Reserved again
[Shield Tablet Android Development] Failrunner:
The portables drivers work for the tablet? The instructions to unlock the bootloader are for the shield portable.
[Shield Tablet Android Development] Unjustified Dev:
Most likely yes and it wouldn't hurt to try. Let me know how it goes. All feed back is appreciated.

The bootloader unlocking part is the same on all devices that allow unlocking the bootloader without some special key you have to request.
[Shield Tablet Android Development] kossiewossie:
works for the shield tablet too. I used the "Universal_Naked_Driver_0.73"
[Shield Tablet Android Development] scorpionx:
That's the command to unlock all the nexus devices as well ;)
[Shield Tablet Android Development] Failrunner:
Yup just unlocked. I knew the command worked. I was worried about the drivers.
[Shield Tablet Android Development] Keithn:
Fastboot drivers are pretty much all the same from my expirence. Sometimes if I'm looking for a driver for fastboot in my list I'll just use one for whatever I see first and Ive never had an issue.
[Shield Tablet Android Development] Unjustified Dev:
Uploaded new recovery.img it's using normal layout as nvidia kernel makes it go that direction I decided to just swap volume up and down keys.
[Shield Tablet Android Development] Keithn:
Just flashed, its good :)

Sent from my One M8
[Shield Tablet Android Development] Unjustified Dev:
[MENTION=335322]MikeChannon[/MENTION] could you move this to the new shield tablet forum please.
[Shield Tablet Android Development] MikeChannon:
Done sir:)

Mike
[Shield Tablet Android Development] les02jen17:
Thanks for creating a forum specifically for the Shield Tablet! ^_^ I haven't got mine yet... still in the process of "attracting" it. :D
[Shield Tablet Android Development] Hashbang173:
Shouldn't this be in the android development section?
[Shield Tablet Android Development] MRobbo80:
Thanks very much, just got my tablet through the post! TOOK 5 days to be delivered (felt like a month) now on to rooting :p
[Shield Tablet Android Development] kossiewossie:
well there should be a section just for the shield tablet... We neeeeed someone to fix it! :p
[Shield Tablet Android Development] Unjustified Dev:
It was moved already it's in android development now
[Shield Tablet Android Development] kossiewossie:
omg. just noticed the tablet has its own section now! wicked!
[Shield Tablet Android Development] bigxie:
Thanks for the custom recovery!

Does anyone have a copy of the stock recovery though? I can't flash an OTA with CWM due to mismatching device name (among other reasons, possibly).
[Shield Tablet Android Development] Unjustified Dev:
Remove the following lines from the OTA zip in META-INF/com/google/android/updater-script

This is an example of the lines to remove.

(!less_than_int(1407012396, getprop("ro.build.date.utc"))) || abort("Can't install this package (Sat Aug 2 13:46:36 PDT 2014) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");

The file beginning line should now read

show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
[Shield Tablet Android Development] bigxie:
Thanks.

Actually, I know of this work around, but I would prefer not to have to go hunting for the OTA URL all the time for future updates, which is why I asked if anyone had the stock recovery.

Anyways, I think it's only a matter of time before Nvidia releases the factory images.

Thanks again!
[Shield Tablet Android Development] Unjustified Dev:
I will have a new CWM up later
[Shield Tablet Android Development] Unjustified Dev:
I'm attaching a new recovery here until it's confirmed working [MENTION=3183886]bigxie[/MENTION]

Let me know how it goes
[Shield Tablet Android Development] Keithn:
The full ota have a different device name and the incremental also have a wrong build fingerprint on top of that. So you can change shieldtablet to wx_na_wf and delete the line looking for a specific build or just delete both. Even with a stock recovery you may run into issues with otas if something like the build fingerprint doesn't match up because you don't have the exact one for the build you are on.

So just fixing the updater script and running it in cwm is probably the best option.

Sent from my One M8

---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------

What's the difference? Change the device in the prop? Still won't do incrementals without modifying so anyone flashing keep that in mind.

Sent from my One M8
[Shield Tablet Android Development] Unjustified Dev:
stock ota uses getprop ro.product.device and expects it to say shieldtablet and my new source reflects that https://github.com/cm-ardbeg/android_device_nvidia_wx_na_wf/blob/cm-11.0/cm.mk#L9

I only seen it check date and device the incrementaal patch is the issue it patches the recovery or at least trys to
[Shield Tablet Android Development] Keithn:
Okay that's what I figured. I'm pretty sure I deleted a line looking for a specific build in the incremental, which would make sense. And yes the ota tries to flash a recovery cwm catches it and you can stop it, the incremental does have patch files but it didn't do anything with cwm for me.

Sent from my One M8
[Shield Tablet Android Development] derking1:
I really hope we get some new kernels and roms for this awesome device (esp. updated sound drivers!!!) The future is bright for this great gaming tablet.
[Shield Tablet Android Development] bigxie:
Thanks Unjustified,

This worked great. I was able to flash both the full and incremental OTA files without alteration.

Is there any way to build in support for the external SD? Keeping large ROM files on internal storage is not ideal for me (and most other users I would guess).

Thanks again.
[Shield Tablet Android Development] Unjustified Dev:
I had no idea it didn't work. I'll look into it soon. What format is your sdcard?
[Shield Tablet Android Development] you5urf:
By default the Shield Tab supports read/write to NTFS/FAT32 for the external sd. Adding support for NTFS in recovery would be the smart choice.
[Shield Tablet Android Development] Unjustified Dev:
I've changed the mount flags to auto so when I release the new recovery it shouldn't be an issue hopefully
[Shield Tablet Android Development] Tsjoklat:
Has anyone tested flashing the recovery with heimdall?

Edit: I was also wondering if a device tree for this device will eventually be added to the official cm11 builds so we can get nightly builds of the recovery.
[Shield Tablet Android Development] cam30era:
Delete
[Shield Tablet Android Development] Keithn:
Don't use heimdall. Pretty sure that's only for Samsung devices in download mode(last I knew it was). From the bootloader use fastboot, it's easy enough.

Merging into CM is being looked into.

Sent from my One M8
[Shield Tablet Android Development] Tsjoklat:
Thanks, I will use fastboot. I'm using latest ubuntu LTS release, but I was not aware that heimdall is Samsung only.

I'm happy to hear that merging to official cm is being looked into.
[Shield Tablet Android Development] Hashbang173:
Once AICP can be built with out any patches to the source I might be able to get Official.
[Shield Tablet Android Development] Unjustified Dev:
The patches I have are necessary there aren't any workarounds to them.

edit: They will get merged by cm in a few days maybe , I am not ready for official support in any rom. Only vanir did it because the creator owns the device. My tree is still being worked on I will pm you when it's ready I had to re-base it on the latest update , I have to rename device trees according to cm , and fix nvidia apps being incompatible on the play store.
[Shield Tablet Android Development] glitchhawk:
the shield portable drivers aren't working for me in fastboot.. only within android. any ideas?

Edit: Never mind. newb mistake... was trying to do "adb devices" instead of "fastboot devices" so... yeah... lol
[Shield Tablet Android Development] Smabbage:
I'm ready to install custom recovery on my tablet but have been hesitant since both CWM and TWRP are both in development stages at this point. It seem CWM is the most developed and reliable of the two. I just need it to basically dump a nandroid to the external SD and install a backup from external SD in the event I mess something up. Is CWM in it's current state able to do this?
[Shield Tablet Android Development] Unjustified Dev:
New recovery image posted with adb working

I merged two patches from bootable/recovery of android's master branch to cwm

* ADB sideload command not work

* recovery: Fix adb with linux 3.10
[Shield Tablet Android Development] Keithn:
I'd recommend cwm for now. The only issue with the newest build is that the sdcard mounting doesn't work properly. The main problem with twrp is not having a functional touch screen in recovery, which makes it useless.

You can backup but you need to use the internal storage

Sent from my One M8
[Shield Tablet Android Development] jaredmorgs:
Sounds like it has come a long way from when I tried it just a few weeks ago. Great work on creating a reliable custom recovery for us!
[Shield Tablet Android Development] Unjustified Dev:
nvm
[Shield Tablet Android Development] MRobbo80:
Good morning still facing the wrong way
[Shield Tablet Android Development] Smabbage:
Thanks for the recommendation. I'm using the Philz variant at the moment and kinda like it. Hope they get 'touch' working soon.
[Shield Tablet Android Development] merhans:
How can I enter the recovery without a system? Power + vol down isn't working for me

...
[Shield Tablet Android Development] minieod:
you have to do it quickly, it is weird. just press the two and let go. it is not standard like every other android device ive ever used where you hold them down til you boot into recovery
[Shield Tablet Android Development] Keithn:
I find that its easy if you just hold the vol button and then tap power and it should go

Sent from my One M8
[Shield Tablet Android Development] abnormaIity:
Yeah that's a best way. Its so sensitive about it its ridiculous, even if I tap it and my finger is on it for just a tiniest bit longer by accident it boots normal. The frustration is real.
[Shield Tablet Android Development] merhans:
This isn't working for me

...
[Shield Tablet Android Development] ShrekOpher:
Hold volume down and the power button. As soon as the nvidia logo shows up let go of the power button but keep the volume down button pressed you will boot into recovery
[Shield Tablet Android Development] merhans:
Doesn't work

...
[Shield Tablet Android Development] Snah001:
Use the Quickboot app from the playstore.

Does all that's needed with an android device.
[Shield Tablet Android Development] jce2005:
Ditto, Quickboot works just fine !!

Now here is a little mystery :

I got the Shield 4G/LTE, rooted it with Towelroot and wanted to install the recovery, but never got ADB Drivers to work to unlock the bootloader and install the recovery image. Well, "Knievel" told me over in the root section that he didn't had to "unlock the bootloader" and got the recovery installed. So I did the same, I just used Flashify, made a backup of my current image, than flashed the recovery.img....... Works perfectly fine without unlocking the bootloader....... BUT WHY ???????

Also got Xposed Framework and GravityBox installed................. Perfectly happy now.

However, I spend almost a day or more trying to get the ADB drivers to work on my computer which I didn't had to do since either unlocking the bootloader is not required or the Bootloader on the Shield tablet is already unlocked.

Got all I wanted for now :

1. Rooted with Towelroot

2. Used Flashify to install recovery image

3. Installed Xposed and GravityBox

Now I am a happy camper ! LOL ;)

Thanks for all the great work to Unjustified Dev !

PS: Screen orientation in recovery is still up-side-down, but works just fine after normal reboot !

Cheers,

jce
[Shield Tablet Android Development] jce2005:
Just found out, that one thing doesn't seem to work while in recovery but it might be a KitKat issue...... A backup made from withing CWM is nowhere to be found.

KitKat changed things on how SD Cards are handled. There is a fix for that on PlayStore called "NextApp SdFix" which I applied to fix the way KitKat handles sd-cards....

But the ClockworkMod folder is empty...... looked around everywhere on the device, on storage, sdcard0, sdcard1 as well as the emulated sdcard, but no backup files for clockworkmod are found..... maybe this can be fixed somehow.....
[Shield Tablet Android Development] KnieveI:
Hi again.

The backup folder is in mnt/shell/emulated/clockworkmod/backup.

Had a hard time finding it myself.

Thanks

Knievel
[Shield Tablet Android Development] jce2005:
Would be cool, if the CWM backup could be directed to the sdcard..... ( sdcard1 ), so a restore could also run from the sdcard.

Maybe "Unjustified Dev" can look into this ! ;)

Thx
[Shield Tablet Android Development] KnieveI:
Hi.

You can already backup and restore to both internal and external sd card.

Thanks

KnieveI
[Shield Tablet Android Development] jce2005:
How ?

THX
[Shield Tablet Android Development] KnieveI:
Hi.

In the backup and restore menu in CWM recovery i can choose between backup to/ sdcard,

or backup to storage/sdcard1.

I always do backup to both, just in case.

Im using v.6.0.5.0.

Thanks

KnieveI
[Shield Tablet Android Development] jce2005:
Well, I can't backup to storage/sdcard1 , comes up with an " error mounting /storage/sdcard1" and if I go to "mount" and try it manually, I get the same error.

EDIT :

I rebooted into recovery again and the backup started this time, but stopped by "Backing up system " Error while making a backup of /system!" so I rebooted again into recovery, mounted "System", but get the same error

Any ideas ?

Thx
[Shield Tablet Android Development] ShrekOpher:
Yeah you need to run the KitKat SD card fix. Then you should have no problem saving to your SD

https://play.google.com/store/apps/details?id=nextapp.sdfix
[Shield Tablet Android Development] jce2005:
Thanks for the tip, but I already applied the sdcard fix ! even checked after flashing recovery and it's still active ! Have no trouble writing to my sdcard when system booted up, also all the other CWM "backup-parts" are on the sdcard, backup just cancels when it comes to backing up "system".

Any other ideas ??

Thanks again,

jce
[Shield Tablet Android Development] ShrekOpher:
What format is the card? My only other guess is that CWM doesn't like the format.
[Shield Tablet Android Development] jce2005:
It's a SanDisk Ultra 128GB....and I think it's fat.... And CWM starts writing several files, before it stops at "system"....

This happens when I select " backup to storage/sdcard1, however, if I connect via USB, there is no clockworkmod folder on the sdcard.

I am now totally confused about the new Kitkat file structure and the fix for sdcards..... [emoji22]

Any other ideas?

Thx
[Shield Tablet Android Development] KnieveI:
Hi.

Did you try another/smaller sd card?

If thats the same i would try to download and install recovery again.

Thanks

KnieveI
[Shield Tablet Android Development] jce2005:
Sorry for the late reply, was real busy with work..... Will try that this Monday or Tuesday and let you know.....

Thanks,

jce
[Shield Tablet Android Development] jce2005:
O.K., so I re-downloaded the recovery image, booted into recovery , inserted a different, smaller MicroSD ( 32GB ) and selected the backup option to sdcard1......

Same happen as with my 128GB card...... it does write several backup files, but aborts by /system with a "Failed" message.

I can do a backup to internal and then afterwards copy it to my sdcard, but it's an extra step... ohhh well...

EDIT : When doing an internal backup to sdcard, the ext. apps don't get backed up due to a " no .android_secure on sdcard1"....... I also cannot manually mount the sdcard1 ! Just seems like clockworkmod backup is not seeing or recognizing the sdcard1 !!!

PS: I will attach the log file from clockworkmod in the morning !

Thanks again.....

jce
[Shield Tablet Android Development] Adrixan:
Is this recovery for the Wi-Fi version only or does it work with LTE too?
[Shield Tablet Android Development] KnieveI:
Hi.

You can use it on Lte too.

But some users reports small issues, its in a early stage of development.

Thanks

KnieveI
[Shield Tablet Android Development] kossiewossie:
Just wanted to confirm to anyone with the LTE tablet, that this recovery works perfectly. I was able to flash it via the flashly and flash superSU, and then flash back to stock recovery without any problems.

So when lollipop hits, you can flash this recovery via adb by unlocking your bootloader and then flash SuperSU v2.22 to root your device.