yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] TheFixItMan:
Im trying to get a visible brightness slider on the status bar of CM11

What I tried to do was take the brightness slider that is already in the quick settings pannel when you select the brightness tile and put the slider itself onto the status bar - Therefore you dont have to select the brightness tile for the slider to appear in a new window because the slider would be on the statusbar itself

so here is my problem - I have got the slider on the status bar and it works in all respects apart from it doesnt actually change the brightness level

So can someone have a look at my xml and work out what needs to be added in order for the slider to change the level of brightness

This is what I have done to get the screen shot results below

in status_bar_expanded under

<ViewStub android:id="@id/ribbon_settings_stub" android:layout="@layout/ribbon_settings" android:layout_width="fill_parent" android:layout_height="@dimen/notification_min_height" />

added

<include layout="@layout/marcus_brightness" />

here is the xml of marcus_brightness

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout style="@style/BrightnessDialogContainer"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
<ImageView android:layout_gravity="center_vertical" android:id="@id/brightness_icon" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/ic_qs_brightness_auto_off" android:paddingStart="8.0dip" android:paddingEnd="10.0dip" />
<com.android.systemui.settings.ToggleSlider android:layout_gravity="center_vertical" android:id="@id/brightness_slider" android:layout_width="0.0dip" android:layout_height="48.0dip" android:layout_weight="1.0" android:layout_marginEnd="2.0dip" />
</LinearLayout>

so my question is what needs to be added/changed to marcus_brightness in order for the slider to change the level of brightness since this xml is basically a copy of the xml which loads then you select the brightness tile and brings up the window with the brightness slider that does work

It looks like toggleslider.smali is just for the slider and does not control the brightness however the xml file for the brightness slider in the tile does not refer to any other smali although there are brightness smali files in smali\com\android\systemui\settings although im not sure how to include these in any layout and I cant work out the reason why the brightness slider works in the tile but not if its moved to the statusbar itself - There must be something that is being refered to that I am missing
[Android Q&A, Help & Troubleshooting] TheFixItMan:
I have now solved this so I am closing the thread

you can see my guide

http://xdaforums.com/android/general/guide-how-to-add-visible-brightness-t2801134
[LG G2 Mini] ariw182:
1.go to www.towelroot.com

2.tap A for download

3. install apk

4. Run the app

5. restart

6. dowload and install SuperSu from playstore

7. Run superSu and update superSu binary if ask

8. Done

DWYOR

Work on my LG-D618
[LG G2 Mini] Vagelis1608:
The " λ " is a greek letter that sounds like " L ".

I don't know why the creator of TowelRoot used it.
[LG G2 Mini] ariw182:
Thanks for correccting me, that letter looks like A :laugh:
[LG G2 Mini] astro cat:
Thanks for this instruction. Root works perfect :)
[LG G2 Mini] ermond012:
It works and was able to do a little customisation on my phone. :D

View attachment 2833267

View attachment 2833268

View attachment 2833269

View attachment 2833270
[LG G2 Mini] ariw182:
Hey i never success to change statusbar icon, i try gravitybox, g2 xposed, g2 tweakbox , it never worked, what module do you use?
[LG G2 Mini] ermond012:
I'm using G2 Tweaksbox.? have you purchased the in-app or pro?
[LG G2 Mini] Mont:
Is not working on my d625 :( says "device is not supported"
[LG G2 Mini] dubisz:
Well, the D625 is a different phone - it's got a Tegra inside.
[LG G2 Mini] rexren:
Thanks , It is work for my D620.
[LG G2 Mini] darth2805:
Can i remove towelroot app after correct rooting ?

btw. maybe they use "lambda" character because they like half-life game.
[LG G2 Mini] Vagelis1608:
Yes, you can
[LG G2 Mini] graco2213:
Can I update phone after rooting him?
[LG G2 Mini] Vagelis1608:
If update manager allows it then you should be able to, but I don't recommend it.
[LG G2 Mini] graco2213:
so I've to choose between updating or rooted phone? im staying with update, maybe after half year we will get 5.0 :D
[LG G2 Mini] chief:
hey, how i unroot my device?

what updates you need? i dont know if you are talking about android or lg updates and why you need them
[LG G2 Mini] barqqlsky89:
Towelroot works great on my stock d620r v10b, but after flashing openEU d620 v10d does not work. Now only works root method by flashing zip.
[LG G2 Mini] graco2213:
Where I can install those buttons? Stock buttons are ugly. I"ve bought xposed
[LG G2 Mini] cripii5:
I have a D625 and the only way I rooted my phone was with Towelroot but only works the v1, not v3.

Here it is, the v1 if someone need it.
[LG G2 Mini] brian88:
Thank you guys, it works great on my D618 :thumbup:

But is there any way to unroot? In case I need warranty

Sent from my Nexus⁴
[Nexus 7 (2013) Original Android Development] shaolinz:
I've never had a touch screen problem
[Nexus 7 (2013) Original Android Development] philseven:
I have had touch issues. Not so much with 4.4.4
[Nexus 7 (2013) Original Android Development] graphdarnell:
Been looking for something like this that embeds all the firmware variants in one package. Guess it's not usable unless integrated in some custom kernel... Will have to wait for aroma installer then. But thanks.
[Nexus 7 (2013) Original Android Development] CTCaer:
Well many have problems and were forced to flash custom kernels with different firmwares.

This can ease up a lot the process and help many people that are using custom kernels to test different fw.

For example many fixed their issues with A011 (aka ts10). Because like in my case, the problem comes from the LCD's electromagnetic interference on ELANtech's touch panel(tested with Nexus 7 Nexus 7 II Tester).

Well it's up to kernel dev's to incorporate the driver mod if they want.

I may make a stock based custom kernel, touch fw tester edition, when I get back home and refix my ubuntu vm.

So 1 flash, try firmwares, find the personal best, reflash previous kernel.
[Nexus 7 (2013) Original Android Development] Trevomader:
Hello, thanks for the patch, i'm using Glitch Kernel which implemented your patch and i'm going to try and fix my touchscreen but i want to know which version of the driver is the latest, is it the A011 or the A044?

And another question, i've just tested A011 and A044 but at vendor both show ELAN_KTF3K_xa064, are they both supposed to show the same version?
[Nexus 7 (2013) Original Android Development] CTCaer:
Yeah both of them show the same version to avoid updating to new one.

I may release an archive with incremental (bigger than a044) sometime.

The latest is A044 since months.

Also thank you for testing this mod.

Good luck mitigating the problem.

EDIT: Checked [MENTION=3847629]Tk-Glitch[/MENTION] kernel commits and corrected the typo to the above patch. Thanks
[Nexus 7 (2013) Original Android Development] trident76:
For the longest time I had crazy touch problems especially when I set the device down on the bed, etc, not unlike many others..but a week ago I pulled my screen protector off and all problems have completely vanished, put another one on, problems return immediately, can anyone explain this? And also is there a screen protector that I can use i.e, tempered glass, for anyone that found the same problem
[Nexus 7 (2013) Original Android Development] graphdarnell:
Some have reported the same problem with screen protectors. I had similar issue with 2012 Nexus 7 when the screen got dirty with finger prints. I now use Nova screen. Lag almost unnoticeable. Matter of fact, it's mostly grounding issue. Too bad there still isn't a way to flash the OP batch, though, according to other threads, the multi-touch fix isn't for that. YAMTT records no problem, but if I leave it flat on a table, some areas don't register touches at all. I've used EMI tape as much as I can see and yet, no improvements. I guess it's between the LCD and the touchscreen. That being the case, no cure.
[Nexus 7 (2013) Original Android Development] raXoN91:
Hi [MENTION=4559618]CTCaer[/MENTION],

I have touchscreen problems on my N7 Flo :crying:. Can you say me how I can test this patch? Or which kernel I must flash? It's there one, which have your patch already intergrated? :confused:

Thanks! :victory:
[Nexus 7 (2013) Original Android Development] CTCaer:
Hey, check 1st post.

I added a list that I'll try to maintain
[Nexus 7 (2013) Original Android Development] godutch:
Do you know if there was a change from android 4.4 to 4.4.2 in the driver? From memory 4.4 seemed to be perfect and around 4.4.2 I started getting problems again (ghost touches)
[Nexus 7 (2013) Original Android Development] raXoN91:
Hey, I fashed the Glitch kernel r151 and the issue is not fully fixed. It's Vetter! But ff the tablet get hot, the issue come again. Is there a special Version with the patch? Thanks :victory:
[Nexus 7 (2013) Original Android Development] CTCaer:
No it's A044. But when I updated 4.4.3->4.4.4, I checked logs and the touchscreen driver wrote something with calibration (can't remember exactly).

The firmwares can't completely fix the problem, only can make the situation better. The device getting hot means that it uses a lot of power and thus more EMI for the touchscreen panel.

You have to test different fw because almost every fw has different internal calibration methods.

Also I learned that the correct way to use the forced calibration (as I mentioned in the other touchscreen problems thread, echo "FF" > /proc/ektf_dbg), is to put the device on an insulated surface, away from power sources, chargers and do it by using terminal emulator and not adb with wifi or cable. And also in flight mode.
[Nexus 7 (2013) Original Android Development] graphdarnell:
I've noticed that Franco's kernel with embedded firmware comes in 2 versions: AOSP and CM. Should I switch between the two, would it be necessary to unlock the patch and reflash it again with the version that corresponds with the new rom? Thank you.
[Nexus 7 (2013) Original Android Development] zaclimon:
AOSP and CM are only the versions that are supposed to match with your rom. AOSP are the majority of the roms you'll probably use. (Stock, PA) CM are roms mostly derived from CM (basically CM, PAC)

In that case you only need to flash the rom if not already done. Then you need to flash the corresponding kernel version and you can use the said patch.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] graphdarnell:
Thanks for the reply. Guess I wasn't very clear. I'm now on CM-derived rom. So I flashed CM-based patched kernel. But if I decide to switch to an AOSP-based rom, do I need to unlock the CM firmware and flash the AOSP firmware instead? Or is it the case that once you flash it, it would stick until you unlock again, no matter what rom you install in between?
[Nexus 7 (2013) Original Android Development] CTCaer:
It locks it. Doesn't matter the kernel. It will only update it if the touchscreen goes into recovery mode.

To unlock it, use A044-unlock.b. This is untouched, so it will show _xA044 in the vendor sysfs and not _xA064.
[Nexus 7 (2013) Original Android Development] Trevomader:
Hello again, yesterday i've tried to "unlock" the firmware, but even after applying A044-unlock.b multiple times it's still showing version 100 (x64) on vendor.

I'm still on glitch kernel, so i don't know if the patch is working correctly on this kernel.
[Nexus 7 (2013) Original Android Development] CTCaer:
Try the attached file. It's stock A011.

If it succeeds and you reboot the driver should then flash the kernel's stock which is A044 (it should show _xa044).
[Nexus 7 (2013) Original Android Development] Trevomader:
Well i just unlocked with "boot-ts-unlock.img", now it shows xa029 and tried to apply A044.b, after rebooting still shows xa029, so maybe the patch is not working on glitch.

Regardless, i'm going to try your new file and report.

Considering the new file is to unlock and mine is already unlocked, nothing to report.
[Nexus 7 (2013) Original Android Development] CTCaer:
well if it was not working you wouldn't had a064 in the first place.

Maybe I'm missing something here. Can you also post logs ([ektf3k] tagged logs)?

The logs style when force flashing is:

"Update touch firmware with the file path:%s"
"Firmware update start!"
"Start firmware update!"
"pages_number=%d"
.
.
.
[LIST]
[*]"Failed the touch firmware update!"[/LIST][B]or[/B][LIST]
[*]"Finish the touch firmware update!"
[/LIST]

Firmware update finish ret=%d retry=%d !"

To check them there are 3 different ways:

logcat

dmesg

cat /proc/kmsg

you can also pipe them to grep ("logcat | grep ektf3k")

Sorry for making you test it, but I'm at my job right now and working since morning
[Nexus 7 (2013) Original Android Development] CTCaer:
Hmm it fails to write the 1st page, 3 times, so it stops trying.

I don't know what causes this...

Btw what version number locking the boot-ts images use?

For example I'm using 99 but it falls back to 64 when showing and checking

EDIT:

Also a successful update should give a ret=0
[Nexus 7 (2013) Original Android Development] Trevomader:
Just installed boot-ts30-lock.img, showing xa072.
[Nexus 7 (2013) Original Android Development] habylab:
So you are saying A011 is the best for you? Why not 44 which has so many fixes? I'm on 44. Never really noticed issues, only from time to time.

I currently have dreadful issues, so excuse this post.

Followed the readme instructions, and it says it could not create the file or folder? What could I be doing wrong?

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3, end of August an HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] godutch:
And between 4.4 and 4.4.2 any differences in calibration?
[Nexus 7 (2013) Original Android Development] Hawke84:
Hi. How can I check what fw version I currently have?
[Nexus 7 (2013) Original Android Development] habylab:
Sad that I couldn't follow these instructions. I'd love to downgrade, as my touch is all over the place at least once a week.

Until there is an easy flash method however, I won't be able to. Have followed instructions as mentioned above, but couldn't pull it off.

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3, end of August an HTC One M8! Tapatalk'd
[Nexus 7 (2013) Original Android Development] Trevomader:
Well, so i ended up with a bricked device, my tablet is stuck at google logo, and through twrp/adb i can see dmesg:

<4>[ 1.053405] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 1.053619] [ektf3k]:[ELAN] Start HW reset!
<4>[ 1.310119] [ektf3k]:The boot code is new!
<4>[ 5.810272] [ektf3k]:[elan] __hello_packet_handler: IRQ is not low!
<4>[ 5.810668] [ektf3k]:I2C message no Ack!
<4>[ 5.810729] [ektf3k]:[elan] hello packet's rc = -22
<4>[ 5.810791] [ektf3k]:Main code fail
<4>[ 5.810913] [ektf3k]:[Elan] Max X=2239, Max Y=1343
<4>[ 5.811370] [ektf3k]:Start firmware update!
<4>[ 5.811431] [ektf3k]:[ELAN] Start HW reset!
<4>[ 5.840270] [ektf3k]:Send command into IAP mode
<4>[ 5.840606] [ektf3k]:Sending packet broken
<4>[ 5.840942] [ektf3k]:Sending packet broken
<4>[ 5.841278] [ektf3k]:Sending packet broken
<4>[ 5.841583] [ektf3k]:Sending packet broken
<4>[ 5.841949] [ektf3k]:Sending packet broken
<4>[ 5.842254] [ektf3k]:Sending packet broken
<4>[ 5.842590] [ektf3k]:Sending packet broken
<4>[ 5.842895] [ektf3k]:Sending packet broken
<4>[ 5.843261] [ektf3k]:Sending packet broken
<4>[ 5.843566] [ektf3k]:Sending packet broken
<4>[ 5.843933] [ektf3k]:Sending packet broken
<4>[ 5.843994] [ektf3k]:Failed sending I2C touch firmware packet.
<4>[ 5.950500] [ektf3k]:Sending packet broken
<4>[ 5.950775] [ektf3k]:Sending packet broken
<4>[ 5.951141] [ektf3k]:Sending packet broken
<4>[ 5.951446] [ektf3k]:Sending packet broken
<4>[ 5.951782] [ektf3k]:Sending packet broken
<4>[ 5.952087] [ektf3k]:Sending packet broken
<4>[ 5.952392] [ektf3k]:Sending packet broken
<4>[ 5.952758] [ektf3k]:Sending packet broken
<4>[ 5.953063] [ektf3k]:Sending packet broken
<4>[ 5.953430] [ektf3k]:Sending packet broken
<4>[ 5.953735] [ektf3k]:Sending packet broken
<4>[ 5.953826] [ektf3k]:Failed sending I2C touch firmware packet.
<4>[ 5.953918] [ektf3k]:pages_number=367
<4>[ 5.954254] [ektf3k]:Sending packet broken
<4>[ 5.954559] [ektf3k]:Sending packet broken
<4>[ 5.954895] [ektf3k]:Sending packet broken
<4>[ 5.955200] [ektf3k]:Sending packet broken
<4>[ 5.955505] [ektf3k]:Sending packet broken
<4>[ 5.955841] [ektf3k]:Sending packet broken
<4>[ 5.956176] [ektf3k]:Sending packet broken
<4>[ 5.956481] [ektf3k]:Sending packet broken
<4>[ 5.956848] [ektf3k]:Sending packet broken
<4>[ 5.957153] [ektf3k]:Sending packet broken
<4>[ 5.957458] [ektf3k]:Sending packet broken
<4>[ 5.957580] [ektf3k]:Failed sending I2C touch firmware packet.
<4>[ 5.957763] [ektf3k]:Failed the touch firmware update!
<4>[ 5.957824] [ektf3k]:Finish the touch firmware update!
<4>[ 5.957946] [ektf3k]: /proc/ektf_dbg created
<4>[ 5.958221] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrupt mode
<4>[ 5.958374] [ektf3k]:[ELAN]misc_register finished!!

Is there a way to fix this? Thanks in advance.
[Nexus 7 (2013) Original Android Development] mdamaged:
[MENTION=4559618]CTCaer[/MENTION], flar2 has patched in the tsfw update into ElementalX.

Source: http://xdaforums.com/showpost.php?p=54706527&postcount=3625
[Nexus 7 (2013) Original Android Development] crazyyyk:
I have the same problem, the same log when I try to update fw with glitch kernel. Why can this happen?
[Sprint HTC One (M8)] bylkaduxx:
hi everyone i'm not sure to be in the good place but i'm from france and i baught a sprint htc one m8 harman kardon edition with bad esn and it's root s'off bootloader unlocked and sim unlocked etc and i would like to know about using 4g or lte with it in france,is it possible?it only works with 3g h or gsm mode but when i select 4g or lte i have no signal ,can someone help me?is there a solution to make it work in france?
[Sprint HTC One (M8)] onefasttreopro:
I believe you need to make sure the French frequencies support 4g Lte...I ran into similar situation when I tried to use my Sprint version in jamaica and read that 4g was only supported on certain frequencies which the phone doesn't have...hope that points you in the right direction...
[Sprint HTC One (M8)] bylkaduxx:
thanks

Sprint one m8: FDD 800/1900 MHz , TDD 2600 MHz and french frequencies are 800/1800/2600MHz so it should work with 800 and 2600MHz right?
[Sprint HTC One (M8)] onefasttreopro:
Technically the 800 frequency tends to be for the voice/2g signals (which you are experiencing) and then the others depend on how the provider is using them specifically...hope that makes sense...probably incompatible frequency usage on the French providers end. Anyone correct me if I'm mistaken.
[Sprint HTC One (M8)] onefasttreopro:
Just did a search and found out Sprint phones specifically use the 1850-1900mhz frequencies for 4g Lte...and France uses 800 (voice/2g) and 2600 for lte...the majority of other European providers use the 1800mhz for their 4g Lte signal...does that help? maybe need to flash French provider software? Only idea I can think of.
[Sprint HTC One (M8)] bylkaduxx:
thanks everyone!

my provider is free mobile and they use 2600MHz only for 4g lte , when i change my sku_id for 9 the 4g logo apear but it's only 3g so i have all the time the "4g" logo but no 4g in real!how do i flash the french provider?

i just wanna say that my problem is only for 4g data.Voice ,text message ,3g all works fine.
[Sprint HTC One (M8)] onefasttreopro:
To flash a French provider Rom you'd have to search around on here or maybe in a local French forum?...that I can't help much with myself...and the frequency for the 4g being different explains why no 4g...that's usually what happens...can only get up to 3g speeds without messing with phone too much. Maybe local phone repair shop can do a flash/conversion for you.
[Sprint HTC One (M8)] bylkaduxx:
if i flash a french provider rom i don't think the rom content that type of configuration/information about frequencies i think it's about anything else,if i erase totaly sprint settings i think it will work but i don't know how to do that,which file in the root do i need to modify.Because this is sprint who did his propoer configuration about frequencies for 4g
[Sprint HTC One (M8)] PAKOS-:
Does 4g Works for your HTC M8 Sprint

HI i want to know does 4g is working on your htc one m8?
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
So, It works ok, no skipping issues, but the sound quality is subpar, even with the bluetooth regfixes. Hard to describe, but there is a hiss or more like a high pitched whine in the background, and it sounds tinny.

My sony ericcson ds970 worked a lot better in this respect, but does it works good as a handsfree set on the tytn? on my previous phone it did not.
[8525, TyTN, MDA Vario II, JasJam Accessories] Sleuth255:
Isn't that a bit of a letdown :( I wonder if the S35 has the same problem...
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
Mr

Well, it'd be interesting to know if others have the same problem, and if people are able to fix the ds970 skipping issues, because it's sound quality is good.
[8525, TyTN, MDA Vario II, JasJam Accessories] darky:
I got the ds970 to work handsfree I even mapped the voice command to it and works like a charm, I still do get the every 30-50 second skip in audio.
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
Mr

So, how bad is the skipping?
[8525, TyTN, MDA Vario II, JasJam Accessories] darky:
it's a one second skip every 30-50 seconds on mp3's,

doesn't skip during voice calls (at least I haven't noticed any)
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
Mr

Tell me when it's fixed or when another as good headset comes out ;)
[8525, TyTN, MDA Vario II, JasJam Accessories] elbowz:
I've used the S35 with my XDA IIi (Alpine), MDA Pro (Universal) and XDA Mini S (Wizard) and on all three I can say that the audio performance is excellent. I suffer no skipping at all.
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
Yes, it's skip free for me aswell, the R35, but the soundquality is pooor
[8525, TyTN, MDA Vario II, JasJam Accessories] zahar:
This must happen on the songs you are playing, or you are an especially keen audiophile. :)

I am listening to Vanessa Mae playing Minuet (WMP) as I am typing this on PIE with my Dopod 838 Pro... there has been no skipping so far and the music I am hearing has no hiss nor is it of poor quality as described.

In all, I think this R35 has been a good companion on my travels so far, giving hiss free and distortion free use, works as a stereo headset as well as voice headset, with my Dopod 838 Pro, and I can even replace the ear buds with ones I prefer, which is a lot more than can be said of existing competing products in the market.

But then again, I am no audiophile and my ears are old, so the lack of quality may be undiscernable to me.
[8525, TyTN, MDA Vario II, JasJam Accessories] grkn:
It's not the songs, and I'm not that much of an audiophile, the stock miniusb headphones sound good enough, maybe you could compare with them?

The r35 sounds much much worse than those.

What rom? do you use btw, I could try yours, I don't know if there could be differences between individual R35s.
[8525, TyTN, MDA Vario II, JasJam Accessories] trentend:
Personally I find that my R35, combined with sennheiser MX500's, gives as good as the built in headphones. I also find that I'm getting good range (circa 5 metres - less range if air isn't the only intervening material - although skipping/noise increases with increased range).

I used the bluetooth and audio mods recommended on the tytn wiki.