yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] :
New Nvertigo Build

New Nvertigo Build up.

post#5

---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------

It'small about freedom of choice: you have the choice between a rom entirely without capacitive buttons (barracuda), and a rom with the choice to dis-/enable it... ;)

---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------

Thanx for your kind words - but first of all: thank you fo your patients with us two thraedjackers!

---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------

Can someone please test:

- BT-Headset

- BT-Keyboard

- HDMI-Out (thinkmsammy hasma prporietary cable for that one - might be wrong)

- all kind of media

Thank you.
[Galaxy Tab S Original Android Development] hurray:
Bluetooth-Keyboard works very well (tested with a MS Wedge Keyboard).

I am on the build from Barracuda77777.
[Galaxy Tab S Original Android Development] Galdan:
Also from me, thank you very very much for the awesome work!

Just a question. Don't know if thats even possible. Wouldnt it be much easier for you to maintain just one build and let the user decide during flashing if he wants to use capacitive buttons or not. Perhaps this would be possible by using "Aroma Installer" or something like this.

Again, kudos from me.
[Galaxy Tab S Original Android Development] johoja:
I can confirm BT-Keyboard works

HDMI-Out - 'KIND OF' works it looks like the color yellow is missing? And audio does not get routed to the tv via the HDMI out - ( the color, and audio ) both work okay with TW Rom. If we can get this to work it would be amazing - let me know if there are any logs I can give that would help.
[Galaxy Tab S Original Android Development] jrock60:
Tested HDMI out on a 10 pin mhl adapter with no luck. same adapter works on htc one m8 gpe.
[Galaxy Tab S Original Android Development] johoja:
I got some output using my cable using nvertigo67's rom - did you get no output at all ? Did the dongle work with the stock rom ? The problem with wtih mine is the color yellow is missing, and audio is not being routed via the HDMI cable ( i think there is currently an issue with audio and BT headsets as well ??)
[Galaxy Tab S Original Android Development] jrock60:
Im running:

cm-11-20141028-UNOFFICIAL-chagallwifi.zip

The cable did not work on touchwiz
[Galaxy Tab S Original Android Development] johoja:
If your cable did not work with TW then it will not work with CM - my cable was working perfectly with TW - and with CM11 ROM its running into the color/audio issues but i still do get an output.

One problem with the BT-Keyboard - in the TW rom when you have a keyboard connected it disables the softkeyboad on the screen ( this doesn't) seem to happen for the CM11 ROM
[Galaxy Tab S Original Android Development] :
Really? On review.cyanogenmod.org there is noe single comit for cm-12.0 and you ask the developers of an unsupported device...

---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------

New Build up. See posting #5.

Happy flashing
[Galaxy Tab S Original Android Development] barth2:
Hello. I asked this in the Q&A thread few days ago with no replies. I'll try it again here.

I have eye problem and the accessibility feature to invert colors (mainly to turn dark text on white background into light text on black background) extremely useful and important. It's invoked with triple click of home button. I think samsung copied it from Apple, and I heartily approve!

It's not standard in AOSP, probably because it requires hardware access. Could this be ported? I think it would be useful to other people as an ad hoc night mode where not supported by specific apps. Thanks.
[Galaxy Tab S Original Android Development] Gilg@mesh:
[MENTION=5697750]barth2[/MENTION] with Gravitybox you can under display tweaks choose solid black background, but I'm not sure if thats what you're after...

Tapatalked from my GALAXY S5
[Galaxy Tab S Original Android Development] PyromaniacGhoul:
I'm sorry if I came across as ungrateful or anything, its just yourself and barracuda know a lot more than I do about what would be needed to get it on our tab one day.

You both have done fantastic work so I imagined both of you devs would be very knowledgable.

But ill not speak of the matter again.
[Galaxy Tab S Original Android Development] reubenskelly1992:
Any chance of the change log? Seems quicker and smoothedf
[Galaxy Tab S Original Android Development] hurray:
Thanks for the new build. The flash was quickly done and the Rom runs good. I made a quick check about the new cpu-settings: now min- and max-frequencies are adjustable. :)

Is the behavior that the range is original (250-1900 MHz) intended?
[Galaxy Tab S Original Android Development] danny19901:
[MENTION=4193974]Barracuda77777[/MENTION] the OP of CM for T700 posted an idea about getting signal etc... Working for T705 maybe worth looking into as it may help T805

This is what he posted anyway

Probably a kernel and a few tweaks to the init scripts for basic radio support. Then changing full_klimtwifi.mk

# Inherit from those products. Most specific first.

$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk)

to something like

# Inherit from those products. Most specific first.

$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] Robin M:
I'm not overly knowledgeable in this area, but I've often wondered why folks would want to tweak their min/max range with the later Android versions and faster multi-core processors available today. Why not just go for a wide range and leave it alone? Seems to me that gives you the best of both worlds... good battery performance most of the time, and fast speed on those occasions when you really need it.
[Galaxy Tab S Original Android Development] naomile:
Any chance that the OP would work on problem with XBMC ? Thanks
[Galaxy Tab S Original Android Development] Barracuda77777:
I have already made quite few builds, with the above mentioned changes, kernel enabled LTE, also with all the relevent changes to the device tree, I have given up for now.

here is the Device tree:

https://github.com/barracuda7/android_device_samsung_chagalllte

until there is a definite way to get it going I can't continue working on it, there are still outstanding issues with the T800 needs to be addressed, like MHL and XBMC touch not responding. Sorry don't have the device, usually I make a build and I test on my tablet, on average I flash more than 25 builds a day to test things, not having the device that means uploading the build, then wait for it to be downloaded and feedback, then start again.....

so please, I respectfully ask not to spam this thread with asking for support for a device our thread never claimed to support, please PM me, and if I have a build or I want to try something, I will pm you a link.

this thread is for T800 WIFI.

Thank you
[Galaxy Tab S Original Android Development] danny19901:
OK I hope someday you's get fully functional T700, T705, T800 and T805 fully working and thanks for all your hard work and to everyone else who is working on these devices
[Galaxy Tab S Original Android Development] maxrdlf95:
T800 its like at 99% except mhl and fingerprint which its like impossible to port
[Galaxy Tab S Original Android Development] Robin M:
I wasn't happy with some things on the generic TW ROM on my T800, so I went looking for something else. After reading all 20 pages of this thread I was impressed by both the accolades that the users gave this ROM AND the extraordinary dedication of the developers. So I just installed the latest Nov 04 version from Post #5 along with the GAPPS from the link on the first post.

I have not installed my apps yet - just looking around getting familiar with the ROM first. (Never used CM before.) I like this ROM a lot so far. BUT one of the first things I noticed was that in "Contacts" all the contact list names were whited out (white print on white background) except the contact that was currently selected. So I want to ask, do other people see this, or is it something I've done? The only thing I changed was to install the Galaxy Tab S theme from the CyanogenMod Theme Showcase (because I missed the wallpaper). I don't think this is the problem however, because the Contacts app appears the same when restoring the original CM theme (and I don't think the theme would effect the app anyway).
[Galaxy Tab S Original Android Development] Barracuda77777:
Please try removing the theme as they do affect built in apps as well and see if this is what causing it, it's not an issue with me all other users contacts displaying as should.
[Galaxy Tab S Original Android Development] Robin M:
That was it. Thanks much! Lesson learned.... don't mess with themes. But now I have got to find that Galaxy S Tab OEM wallpaper. ;)

Question... With this ROM I guess there is no way to set a wallpaper on the lockscreen that is different from the home screens, correct?
[Galaxy Tab S Original Android Development] :
Recall from memory, so may be I'm wrong: sammy rom has no inverted colors, too. In kernel config we have MDNIE_LITE and not MDNIE (that's for sure) and therefore we have no option on kernel level to invert color. May be one day, but other issues have higher priority. Sorry.
[Galaxy Tab S Original Android Development] Barracuda77777:
go to themes and then click on change locksreen Wallpaper.
[Galaxy Tab S Original Android Development] :
No, no, not ungrateful... ...more kind of amusing... ...we are not allmighty with sourcecode growing from our pockets. Let's first concentrate on ironing out the issues of cm11 for t800. If cm12 arrives, we will see.

---------- Post added at 05:37 AM ---------- Previous post was at 05:30 AM ----------

I tried to put the -H (human readable ;) ) changelog in #5. The expert changelog is in my gits: click on "commits". My last build is,buildmfrom the branch "my-work". If we don't have any regressions, I'll put it all in "cm-11.0" branch. You are all invized to lool in our gits and fork them and build and suggest fixes and enhamcements.

---------- Post added at 05:40 AM ---------- Previous post was at 05:37 AM ----------

Yes. Imsaid it'smadjustable, not over/underclocking etc... I want to have the issues fixed, befor merging new issues in... ;)

---------- Post added at 05:46 AM ---------- Previous post was at 05:40 AM ----------

...'cause we don't came up with a fix, doesn't mean we are not working on it. As I said before: sourcecode does not grow from our pockets...

---------- Post added at 05:51 AM ---------- Previous post was at 05:46 AM ----------

Sorry, 1,8 GB are out of my 3g data plan. Didn't know when saying I will dig into. Perhaps barracuda can jump in, please?
[Galaxy Tab S Original Android Development] Barracuda77777:
I will download asphalt 8 and see how it runs compared to Sammy rom.

really though, this is a hardware issue and not cm, I think our time is best served if we concentrate on getting all features working for now, like Mhl and xbmc,. will see.....
[Galaxy Tab S Original Android Development] Robin M:
Thanks once again! And thank you for all your hard work on this ROM and for being so responsive and eager to help.

.... and I found my Galaxy S Tab wallpaper right here on this forum. :)
[Galaxy Tab S Original Android Development] SS2006:
Would this work on the 8.4 WiFi :) or anything like it
[Galaxy Tab S Original Android Development] :
Wrong thread. There is an other thread for the t700 port.

---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------

Does touch input work on sammy rom?

Does bt-keyboard input work on our rom for xbmc?

---------- Post added at 07:33 AM ---------- Previous post was at 07:31 AM ----------

Whats about camera2? Does it work for you with my latetest build from yesterday from #5?
[Galaxy Tab S Original Android Development] Barracuda77777:
XBMC fully works with sammy, I just tried my bluetooth keyboard with our rom and I could navigate in XBMC, so this is great, as a temporary fix, users who wish to use XBMC with our rom can use a bluetooth keyboard or a usb one.

will update OP with this information

so...

I downloaded asphalt 8 airborn on my tablet and my friends, ran them side by side, with samsung firmware the game ran much smoothers than ours, there is definitely a 30% less performance with our rom in this game, played some other games and performance was top notch comparable to samsung's rom. will need to do further digging to look into it to see if this is due to the kernel or the rom istself.

just did antutu benchmark on smasung rom and ours.
[Galaxy Tab S Original Android Development] danny19901:
If you have graphical issues in landscape with statusbar disabling HW overlay fixes it as I have T705 and using T700 cm11 ATM but I noticed that on my Xperia Z some roms used old blobs .233 blobs and had issues with hover and few over things caused screen flickering but newer blobs fixed the issue but also disabling HW overlay also fixed the issue I hope this kinda helps

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] hurray:
I read it too slow but yes: my bluetooth MS wedge keyboard is able to control xbmc 13.2 and Kodi 14 Beta 1 (I just test it).

The near full navigation can be made via the cursor buttons, enter and escape.
[Galaxy Tab S Original Android Development] ramiss:
The quote below is from another thread on choppy gameplay. The temporary fix for now is to force the cpu to full with SetCPU or some other util.

I mention all of this because this is exactly the thing we need a new kernel/rom to solve.
[Galaxy Tab S Original Android Development] Robin M:
Bluetooth Won't Turn On

After a complete wipe and flashing this ROM (Nov 4 version), I cannot get Bluetooth to turn on. When I move the slider from OFF to ON, screen says "Turning Bluetooth On...." but it times out after about 8-10 seconds and never works. Wiping Cache and dalvik-cache made no difference. Bluetooth worked yesterday on stock Samsung ROM.

Everything else seems to be working fine. Haven't seen anyone report a BT issue. Has anyone experienced this, or does someone have a suggestion as to what I can try to get BT working?
[Galaxy Tab S Original Android Development] ramiss:
Try clearing both System and Dalvik Caches.
[Galaxy Tab S Original Android Development] Robin M:
Just tried that before posting. Made no difference.
[Galaxy Tab S Original Android Development] Crimsonthunder:
Is there a way to enable it. Or did Samsung disable it in the hardware?
[Galaxy Tab S Original Android Development] :
To much sepolicy cleanup. Found the missing line - fixed in tomorrows build.
[Galaxy Tab S Original Android Development] :
In deed it was missing PARANOID_NETWORK in kernel config. Fixed. Uploading. 20 minutes left.

---------- Post added at 11:43 PM ---------- Previous post was at 11:10 PM ----------

BT working. I'll put the bugfix-build here. Changelog and synced clean build tomorrow (@barracuda: this is only for fixing bluetooth, therefor not in #5 - will document and update tomorrow.)

ROM:http://charlesingo.mine.nu/ftp/nvertigo//cm-11-20141105-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5:http://charlesingo.mine.nu/ftp/nvertigo//cm-11-20141105-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum

Worked for 14 h on rom - need a break.

Good Night, Nvertigo
[Galaxy Tab S Original Android Development] Robin M:
That was quick. Thanks!!

Question: When going from the current version of this ROM to the latest update, what is the recommended wipe procedure? Would it be cache and dalvik-cache only?
[Galaxy Tab S Original Android Development] Barracuda77777:
for super clean update:

cache, delvik, system,

you then flash:

rom

gapps

optional supersu

op updated with links to nvertigo67 latest build.
[Galaxy Tab S Original Android Development] danny19901:
I'm surprised you's haven't skipped this and went to work on L unless you's are

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] suzook:
L???? We need source for l, which hasn't even been leaked for Sammy. This is a cm thread, and there is no cm12 yet..let's be happy with cm11!
[Galaxy Tab S Original Android Development] Robin M:
Thanks. That reply brings up a few additional questions, though.... Not to question your advice, but to satisfy my curiosity, if you would be so kind..

1. Does wiping "system" overwrite all your user apps and settings, or does that only happen when you also wipe "data"? (I can't remember.) Also, what about page layouts, home page folders and widgets?

2. Same question as above with respect to re-installing gapps.

3. How do you flash "supersu"? That has always been my choice of su apps, but when you download it from the market it never appears in the app drawer, and you cannot invoke it. The built-in su always takes precedence.

Thanks, Rob

BTW, 05112014 did indeed fix the BT problem. Thanks again to Nvirtigo67 for being so quick to jump on that!
[Galaxy Tab S Original Android Development] :
Flashingnsystem does neither wipe settings, nor apps

Google "chainfire supersu flashable zip" (put these four strimgs without the quotes in google)

BTW: regressions sucks. It was my fault not checking every single patch I put in kernel.
[Galaxy Tab S Original Android Development] :
To get the phrases right:

Very dirty flash:

flash rom

flash gapps

[optinal but recommended for some apps to work i.e. Titanium] flash chainfires SuperSU

Dirty flash:

[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system

wipe cache

wipe dalvik-cache

flash rom

flash gapps

[optional] flash SuperSU

Clean flash

factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps

[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system

wipe cache

wipe dalvik-cache

wipe data (without wiping /data/media) this resets your settings and deletes your installed apps

flash rom

flash gapps

[optional] flash SuperSU

Very clean flash

factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps

[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system

wipe cache

wipe dalvik-cache

wipe data (without wiping /data/media) this resets your settings and deletes your installed apps

wipe internal memory

flash rom

flash gapps

[optional] flash SuperSU

I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.

On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?

I count on users good judgment - all participants on this beta-test has shown this so far.

BTW: Thank you for helping making this rom better!

Nvertigo
[Galaxy Tab S Original Android Development] danny19901:
L sources are out has nothing to do with Sammy as sources come from Google people could start working on AOSP rather than wait for CM12 I have L on my Xperia Z built from sources everything nearly works for it

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] Laykun:
Like with most Android releases there a certain new kernel features that come along for the ride. In this case we need a leaked rom from Samsung to get an updated version of the kernel with the feature set required to run Android L. I'm not entirely sure that this is the case but it certainly has been in the past.
[Galaxy Tab S Original Android Development] danny19901:
I'm sure kk kernel will work with L maybe with a little tweaking as I know Xperia z has L working and using a different kernel from what L should be using

Xperia z is using 3.4 kernel for L were as we need to wait for 3.10

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] suzook:
OK then. You will have this done for us today???:rolleyes: Thanks we appreciate it.
[Galaxy Tab S Original Android Development] :
Android L

I understand the hype on Android L. And I encourage everybody to go for it.

For myself I have to state I will wait for cm-12 before wasting a single thought on porting Android L to chagall. We have lots of issues in this beta state rom. I will concentrate on getting cm-11.0 fixed and optimized. So please read the subject of this thread and stick to it.

I said many times: take my gits and do what ever you want to them. Port it to IOS if you want... You can open then a new thread. You can also open a new thread for theoretical discussion on old kernels and new OS. But my work will be on cm-11.0, at least 'til cm-12.0 M1 is out. And then there will be a new thread.

Of course I can not speak for OP - all of the above is my humble opinion.

Thank you for your oppinions.
[Galaxy Tab S Original Android Development] danny19901:
I would love to try build L but I don't have a decent PC or laptop to try build with

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] :
New Build.

New build up in #5. Mainly the same as yesterdays bugfixmbuild, but repo synced and clean build.
[Galaxy Tab S Original Android Development] suzook:
Couldn't agree more! You have done awesome work. Everyone has an opinion on how easy it is, yet they dont/can't do it. Cm11 on this thing is perfect!

---------- Post added at 08:26 AM ---------- Previous post was at 08:24 AM ----------

Put up...or shut up. Move along. This is a cm11 thread.
[Galaxy Tab S Original Android Development] reubenskelly1992:
Agreed, this ROM is amazing. They can't build on something that's not even available yet
[Galaxy Tab S Original Android Development] danny19901:
Thing is I'm not talking about CM12 and yes L is out http://xdaforums.com/showthread.php?t=2929369 as seen here Xperia Z has it all it may take is building from sources and doing a little work I didn't mention CM12 im meaning pure AOSP I'm surprised they haven't tried to build yet

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] :
Thank you very much for your oppinion. I appriciate your oppinion.

Porting an existing cm to this tab is often behind my limits. Making a cm of android scorces is FAR behind my abillities. So please resepect my decission developping cm-11.0. Please resepect the subject of this thread.

So far for the polite and respectful way of communicating that this is the wrong thread for the discussion you are starting of. Thank you for understanding that.
[Galaxy Tab S Original Android Development] danny19901:
Ok sorry I was just curious that's all and I appreciate all the work going into T700, T705, T800, T805 and a big thanks to all devs who are working hard on these

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] reubenskelly1992:
You do it then
[Galaxy Tab S Original Android Development] danny19901:
As stated before if I had a decent PC or laptop I would try and build

Anyway i was looking around to see what has L Xperia Z does and

S5 does Samsung Galaxy S5 | Android L 5.0 ROM | Download: http://youtu.be/6pQgkngBe4k

If the S5 would be any help to development

http://gripfiles.co/146087

But this shows that we won't need Samsung to release

TAPATALKED WITH MY TAB S 8.4
[Galaxy Tab S Original Android Development] reubenskelly1992:
Sure
[Galaxy Tab S Original Android Development] :
Sirs, please - dont make this a L thread.

I don't mind one or two OT posts. But these theoretical AOSP L fantasies take now more them a page of posts - this is highly disrespectful to everybody, who wants to use and discuss our rom. I think evenmthe new version posting gets messed up with this L-S+@#! Go else where. Make a L-thread but leave us alone here. You mustn't use our rom, but go away with AOSP L talk. Thank you for your understanding!