yashsingh1/xdaforums huggingface dataset:
[HTC 10 Questions & Answers] davm7488:
This has been a bit of an ongoing issue with seemingly no solution.

I started out by flashing viper10 2.5(then current) using twrp 3.0.2-5 as my recovery. Everything worked fine for a few days. Boots were normal. I installed xposed v86. Along the way I realized that I had adaway 3.11 installed but not activated. After I activated this, I started getting the optimized apps on boot.

I first assumed it was because i modified the HOSTS which lives on /system. A few threads popped up in the search engine here to support this theory. They come from the Nexus6P, Moto and Sony Z3 subforums. Nothing for a recent lolipop HTC phone

-wipe cache

- format data

- changed roms from Venom10 to Leedroid

No dice. 20 apps optimize on boot after each step taken.

Another working theory I have is that there are remains of xposed on my phone that was not uninstalled properly. There are a few scattered posts here, on Android central and on the Github that say an improper uninstall(or lack-thereof) can do damage.

- I tried taking a logcat with ADB, but it only starts capturing after I input my pin for decryption

- I can make no sense of it, but the top line does read "Beginning of crash" The entire file is slightly too large to upload at 612kb and i dunno what would be ok to trim.

If I go back to stock with the US unlocked RUU this disappears. As soon as Iunlock, root and flash a rom 20 apps need to optimize.

If anyone has anything I havent tried I'd greatly appreciate it.
[HTC 10 Questions & Answers] suhridkhan:
Are you restoring your apps with with TitaniumBackup or something when you switch between roms?

What if you uninstall one of those 20 apps that are optimizing? Is it now 19 apps that optimize?

I recommend clean installing some of those apps and see what happens.
[HTC 10 Questions & Answers] afuller42:
reinstall viper 2.8 with a full format & wipe
[HTC 10 Questions & Answers] davm7488:
i'm restoring apps from the Google/HTC interface. My phone says there are 87 to install. I'll try another flash without bringing any of the apps over.
[G Pad 8.3 Q&A, Help & Troubleshooting] mikekoz:
I have had this tablet for about three years now I guess, and over the past few months, it has developed an odd problem. When first turned on, the brightness is at a normal level. Once you stop using it and the screen goes into a sleep mode, the brightness will be about 50% dimmer when it wakes. The brightness setting does not change, just the brightness itself. A restart fixes it until it sleeps again. I am rooted on 5.02. I tried a LG brightness patch that supposedly fixes an issue with this tablet caused by overheating, and that did not work. The problem could not possibly be being caused by overheating since it happens even after it is turned off for a while. I could try a hard reset of the tablet, but I am afraid it would break root on the tablet. I had a hard time rooting it and would prefer to find another solution! Thanks in advance to anybody that can help!
[G Pad 8.3 Q&A, Help & Troubleshooting] roirraW "edor" ehT:
Sorry, no idea that doesn't begin with flashing the 22B TOT and/or the 11A KDZ to start fresh.

Hope you find your solution.
[JAMin, XDA Neo, S200 General] enduromen:
hello

Maybe if what i ask is too complcate but insted wask for a wm6 Portuguese rom i prefer some help that can make me possible lear about how to translate a rom for my own language.

If possible i want to known want soft i have to use and the process to translate. I think this can do a lot of work but i´m ready for it. I just need some light how to begine.

If there are so kind of tutorial were great

Best regards

enduromen

sorry for my bad inglish
[Moto 360] billyli19:
Hey guys, my moto 360 started to act weird or getting dead pixels (what I think it is) suddenly. Can you guys please confirm if this is "stuck pixels" or "dead pixels"? There are blue, green and red dots at 5o clock. Rebooted the device a few times and still no help. Thnx
[Android Q&A, Help & Troubleshooting] Moyin99:
Hey,

I'm using a Samsung Galaxy S3 LTE (i9305) at the moment, on which I tried to install TWRP and CM13.

At first the installation of TWRP did not work - after that, the SIM card didn't work as the cellphone made a restart into the system.

After a little bit of research (and a few videos on YouTube) I managed to install TWRP and installed CM 1 3 (unofficial) on my phone.

After a restart my phone was stuck in bootloop - the CM logo was only shown at the start and did move.

I made a factory reset after that and tried to install TWRP again, this time with CM 11 (official) - with the same problems as before.

After I installed CM 11, Windows shortly recognized the phone when it booted - but I don't know, if my PC would have recognized the others too (Windows just played the sound it does, when a new device is connected)

The TWRP version is 3.0.2-1.

Any idea what I could try now?

Thanks in advance!
[XDA Assist] turtallll:
Well I screwed up while rooting my htc one a9.

While installing TWRP in command prompt I typed:

"fastboot flash boot twrp-3.0.0-3-hiae.img"

instead of

"fastboot flash recovery twrp-3.0.0-3-hiae.img"

Now whenever I boot my system normally it takes me to TWRP recovery. I couldn't find anyone with the same problem, sorry if this is answered already.
[XDA Assist] turtallll:
fixed...

found out the reason i couldnt flash a new boot image was because apparently I have to be in download mode while I was in bootloader.
[XDA Assist] jackeagle:
Glad to see that you found the fix for your problem.

Thread Closed.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] spaghettibounce:
So I rooted my Thor, got safestrap, downloaded Kitkat (fire nexus), Installed Xposed, and now I'm here. I managed to reskin the soft keys to look like the lollipop ones, but I really hate how the navigation bar stays at the bottom of the screen when in landscape! It takes up so much valuable real estate for three buttons. Is there any way to make it move to the side when in landscape, like it does in the FireOS or on phones?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Not that I have found - at least in a satisfactory manner. Gravitybox (Xposed module) has an experimental option but it is ineffective on this device/rom. However, GB also allows resizing the nav bar and adding an additional soft key which helps take up some of the slack space and adds useful functionality.

Phab7 (an old Xposed module) does move the nav bar to the right but the other effects offset the benefits IMO.
[Moto G4 Plus Questions & Answers] DJTeeJay:
I've never ran into this issue all the Android Devices I have owned. I'm hoping it's something simple yet annoying as fukc. Not sure if it's a TWRP issue ? SuperSU (latest version after update) is there and it shows as all apps are Granted su permissions.

As of right now, I'm back to my original stock MPJ24.139-49 , with unlocked bootloader. I am seeing a few different SuperSU(s) in the threads to flash. I would just flash stock firmware but trying to get to file is a pain in the ass.

Any help greatly appreciated...
[Moto G4 Plus Questions & Answers] D1AMONDH3AD:
https://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip this works for me and i also restored from nandroid backup and didn't lose root so yeah try it u don't need to patch boot.img or anything just flash it with twrp dats it
[OnePlus 2 Android Development] GuestK00293:
Let us get back once the CM14 nightlies start

Unofficial CM14 builds based on CyanogenMod + Grarak + Cherry-pick from CyanogenMod review stream

Facts:

Added 1 blob from OOS 3.1.0 to get the build working (Grarak is aware of it)

No extra features added, please do not request (still a n00b here)

Focus is more on debugging and hopefully help Grarak

Why is it not my daily driver though it is stable enough for a daily driver:

Unable to deactivate a SIM (just my itch)

Video recording does not work (Footej works but I want the stock camera to work: Will debug)

Busy to be able to spend more time debugging (especially with many other components changing rapidly)

Note:

Thank you all for being nice on this thread
[OnePlus 2 Android Development] hanaxxaru:
i would say, your hack is working just like your username.. :D
[OnePlus 2 Android Development] Mohit31:
Is it possible for you or anyone to make a flashable zip of the fix...!?

Would be much better and convenient

We can use it on any ROM and will not restricted to use above 2 ROMs only
[OnePlus 2 Android Development] GuestK00293:
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.

I have done something similar by intercepting IO requests to speed up IO over network
[OnePlus 2 Android Development] Mohit31:
Lol... It all went above my head :p

I think the answer is, it's not possible, right?
[OnePlus 2 Android Development] PeterImmel:
Thank you very much. It's working for me.

(I guess next/about next will have the fix, too. The existing commit only has to be merged)
[OnePlus 2 Android Development] lalit.kultham:
Great work! This bug has been present since ever.
[OnePlus 2 Android Development] PeterImmel:
Todays build doesn't have the fix already. Am I right?
[OnePlus 2 Android Development] GuestK00293:
Getting a patch merged is a slow process especially with almost all of CM devs focussing on 'N'. I will make a new build available with patch to hide signal for deactivated SIM in the status bar (when I get back home from work). There are/were 2 issues bugging me for a long time.
[OnePlus 2 Android Development] GuestK00293:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.

Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
[OnePlus 2 Android Development] Mohit31:
That's awesome

Great work

Thanks a ton..!!
[OnePlus 2 Android Development] thdervenis:
You 're the man! Back to CM13 because of your fixes. Many thanks!
[OnePlus 2 Android Development] lalit.kultham:
Any chance of fixing loudspeaker echo, WhatsApp voice note not loud and random vibrations due to dt2w?

With these fixed, CM will be bug free.
[OnePlus 2 Android Development] raburs:
[MENTION=2618159]hackworks[/MENTION] Has the rom been built with latest aospa code?
[OnePlus 2 Android Development] Mohit31:
You have fixed some of the very irritating bugs..

I wonder if you can do your magic on this issue as well..

http://xdaforums.com/showpost.php?p=67812802&postcount=1554
[OnePlus 2 Android Development] raburs:
Yea. :/

This has still not been fixed.

http://xdaforums.com/showpost.php?p=67812802&postcount=1554 [MENTION=2618159]hackworks[/MENTION] Please have a look.

P.S. This issue isn't present on AOSPA. So maybe that'll help.
[OnePlus 2 Android Development] John-J.Hammy:
Can i flash Xposede Framework?

Gesendet von meinem ONE A2003 mit Tapatalk
[OnePlus 2 Android Development] GuestK00293:
It is just CM13 with the 2 fixes. All that applies to CM13 or AOSPA remains valid on these builds
[OnePlus 2 Android Development] GuestK00293:
n00b here. No magic, just learning. I am working on using a cleaner approach to hide the SIM signal icon. Once done, will explore other areas
[OnePlus 2 Android Development] GuestK00293:
Sorry for not responding earlier, I have uploaded a new build which is based on latest source as on today 26th Aug 2016 (night) for both CM13 & PA.

I tried my hands in Java code by implementing an event based mechanism to disable the SIM icon when it is disabled - Just ended up in flickering display and a SystemUI crash! Guess, I should just stick to C/C++ where I have spent most of my programming life (~18 yrs)! Summary: Will pick areas/bugs based programming language, no time to learn Java
[OnePlus 2 Android Development] nicesoni_ash:
[MENTION=2618159]hackworks[/MENTION]

Hi,

Merged your changes with my build that's for a dual sim phone, OP2 based on CM13.

Hiding SIM icon is working for first sim only, not the second one. Is that supposed to work like this?
[OnePlus 2 Android Development] retaliator:
I flashed your CM13 unofficial rom but the compass stays broken. Is there anything more to do than just flashing rom and gapps?

Thanks in advance.
[OnePlus 2 Android Development] :
That is very strange! You seem to have done everything on your side. Did you wipe dalvik & cache just to make sure nothing is stale from the previous flash?
[OnePlus 2 Android Development] :
I am able to hide the second SIM.

[The SIM hide code is from [MENTION=5083850]Thecrazyskull[/MENTION], I just took that change from AOSPA and resolved the merge conflict]
[OnePlus 2 Android Development] retaliator:
yes I did. Maybe I should flash the original software again.

My last change before I get another smartphone...
[OnePlus 2 Android Development] nicesoni_ash:
Strangely it's working now.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[OnePlus 2 Android Development] Thecrazyskull:
If you don't mind, can you show me what you've done for a proper solution so far?

Thanks.
[OnePlus 2 Android Development] :
My first attempt coding in Java & approach I was exploring (stash based off CM13): http://pastebin.com/CQwExaEA
[OnePlus 2 Android Development] Thecrazyskull:
This approach is wrong.

What danny meant with his comment on gerrit was that cases like these should be handled on telephony level (frameworks/opt/telephony) instead of systemui (like we did).

I'm not good enough with android telephony to figure this out, so i just left it as it is.

Please let me know if you know of a way to handle this properly on telephony level.

Thanks.
[OnePlus 2 Android Development] mr_krabbs:
perfect

works great! this bug is so annoying!

there were some cm13 official releases which worked. but the bug was never fixed in new releases

much thx for this here buddy!
[OnePlus 2 Android Development] :
I have built a stand alone library that should fix this problem on any MM ROM. Have not tried it myself.

Link: https://www.androidfilehost.com/?fid=24651430732237305

1. Download the tar.gz on your computer

2. BACKUP YOUR ROM IN TWRP (or any recovery)

3. Untar the contents and copy the contents onto your system partition at the same path. This will overwrite the library built by custom ROMs

- system/lib/hw/sensors.msm8994.so

- system/lib64/hw/sensors.msm8994.so

4. Make sure the permissions are proper (just look at other libraries) - "chmod +r"

5. Reboot and it should work - If not, please let me know
[OnePlus 2 Android Development] Mohit31:
Thanks...will try and revert back :)

---------- Post added at 06:56 AM ---------- Previous post was at 06:43 AM ----------

Any idea how to untar the contents..

Its getting saved as sensors.msm8994.so.tar after untar

Edit: Got it..will try now

Edit 2: [MENTION=2618159]hackworks[/MENTION] You are AWESOME

Thank you soooo muchh

Damn, that feels so good

Will see how it behaves after reboots...will test it thoroughly and will give further confirmation

Thanks again
[OnePlus 2 Android Development] PeterImmel:
Heyhey. I've been on holiday for 10 days now. Is the rotation vector fixed on official builds already?

(sorry, I'm too lazy to read the official thread right now. So many pages....)
[OnePlus 2 Android Development] :
I have made a flashable zip with rotation vector fix. I've implemented a sensor proxy to filter out the buggy sensor. This has been tested on CM13 and it works. Based on the implementation, it should work on *ANY* ROM for OP2

Download the zip and flash it over existing ROM: https://www.androidfilehost.com/?fid=24686680535467373
[OnePlus 2 Android Development] Mohit31:
Thanks for the efforts and making our life really easy.. :)
[OnePlus 2 Android Development] thdervenis:
I tried it on RR Official, rotation vector did not work before, it works now. Many thanks.
[OnePlus 2 Android Development] :
Thank you for the feedback. My sole intent implementing a fix using the approach of intercepting was to make sure it works on as many ROMs as possible. Looks like it is happening!
[OnePlus 2 Android Development] Gaffadin:
This worked perfectly in Seraph's CM13.

Thanks!
[OnePlus 2 Android Development] thdervenis:
I guess one of your changes is merged and will be available on the next nighty.

https://review.cyanogenmod.org/#/c/159438

Am I correct to assume that this will fix the rotation vector on CM13 "officially"?
[OnePlus 2 Android Development] Thecrazyskull:
No, we are waiting on http://review.cyanogenmod.org/#/c/160062/
[OnePlus 2 Android Development] Mohit31:
[MENTION=2618159]hackworks[/MENTION] [MENTION=5083850]Thecrazyskull[/MENTION]

Now that the rotation vector bug has been completely fixed, can you guys fix this problem as well

http://xdaforums.com/showpost.php?p=67812802&postcount=1554

Doesn't happen on aospa or du but happens only on cm based ROM

Hope you guys can look into it and fix this issue as well

Thanks
[OnePlus 2 Android Development] nicesoni_ash:
Just tested and no such issue here.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[OnePlus 2 Android Development] Mohit31:
Its there..!!

Follow this steps to replicate the issue

Enable on screen navigation and disable hardware keys

Now try to operate your phone keeping FP home button pressed

It behaves as if the button is still active

You will see glitches/lags while operating the phone
[OnePlus 2 Android Development] :
I confirm, the scrolling gets messed up. It recovers immediately when you lift the finger from the hardware button. It happens when the finger is on any of the hardware buttons. We might have to look at the kernel for this. I will try my best. The code to disable hardware button is just writing to sysfs and the kernel handles this.
[OnePlus 2 Android Development] Mohit31:
If it needs any kind of testing, do let me know

Thanks..!!

Edit : ROMs like tipsy, dirty unicorns, aospa don't have this bug when you disable hw keys, if that helps
[OnePlus 2 Android Development] nicesoni_ash:
I am on rr and I dont have this issue. I tried with all three hard keys. Not a slingle glitch. It may be in clean code only like cm.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[OnePlus 2 Android Development] Mohit31:
That's strange..!!

When I was last on RR (shreesha's builds ), it had this problem.

Are you on Rajgopi's RR..?
[OnePlus 2 Android Development] nicesoni_ash:
Nope, I am on my own built build that's based on rr sources.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[OnePlus 2 Android Development] :
If you read the documentation at https://developer.android.com/reference/android/telephony/SubscriptionManager.html#getActiveSubscriptionInfoList(), it says that function will return information of *ALL inserted* SIMs. If that is true, we will need to register to a callback to detect change and maintain a array booleans for 2 entries (for 2 slots) and store the state. This can be used in the status bar refresh code. This will avoid the RPC and is more callback/event based mechanism.
[OnePlus 2 Android Development] :
Could you please share the kernel source for your build without the problem? I am seeing a pattern and will try a small change in the kernel - gut says it will fix, reality might be different though :)
[OnePlus 2 Android Development] Thecrazyskull:
IMO qualcomm should fix this inside extphone by properly getting rid of the disabled simcard instead of marking it as "NOT READY" so i'm not sure if there even is a proper aproach outside of extphone.

But as i said, i'm not that good with telephony so i'm not the one to judge that :)
[OnePlus 2 Android Development] nicesoni_ash:
I use default cm Kernel tree but I am using benschhold Kernel...

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[OnePlus 2 Android Development] raburs:
This issue is still present in most of CM/CAF based ROMs out. Whether it is halogen, rr, cm, aokp etc.

Maybe it's a kernel issue

This has not been fixed.

AOSPA doesn't have any issues like this.

[MENTION=2618159]hackworks[/MENTION] Should have a look at this.
[OnePlus 2 Android Development] nicesoni_ash:
[MENTION=2618159]hackworks[/MENTION]

Since you implemented a new cleaner method using a wrapper, should I uncommit the changes I made earlier before cherry-picking this new approach?
[OnePlus 2 Android Development] :
Yes. Grarak has cleaned it up: https://github.com/Grarak/android_d...mmit/a3ab0a5ed3a1074df3914cfef2f1a155fdbf69c7
[OnePlus 2 Android Development] Mohit31:
I am currently on your RR build with benschhold kernel and I do have that hardware key bug, the one I was talking about :rolleyes:
[OnePlus 2 Android Development] nicesoni_ash:
That's indeed strange 'coz I tried with Bens as well as my stock kernel and didn't face this issue.
[OnePlus 2 Android Development] Mohit31:
Never mind, this seems to be there in all cm based ROMs

Hopefully will be fixed in cm14

BTW your build is damn good

My new daily driver

Hope you will continue with the unofficial builds of rr

Btw is it possible to implement seraph slider options in your unofficial builds..?

Thanks
[OnePlus 2 Android Development] nicesoni_ash:
Could be a kernel issue not the rom issue but yeah hopefully cm14 may fix it for you.

Let's keep this conversation in Unofficial thread and yeah, extra options are coming soon. Hopefully in next build which is coming tomorrow.
[OnePlus 2 Android Development] :
Our maintainer [MENTION=4443334]Grarak[/MENTION] has merged (along with cleaning it) the rotation fix into CM13. Next nightly should have it. This was a short lived thread with no future use
[OnePlus 2 Android Development] Mohit31:
If you happen to talk to Grarak, can you inform him about the hardware key bug as well..!!

I know it's not a big deal but it's good to have all the issues ironed out

Thanks
[OnePlus 2 Android Development] mdaamir1989:
Short lived but a very important one for most of the users if not all , thanks to you and everyone who made this possible :)
[OnePlus 2 Android Development] crash4fun:
I appreciate all efforts in making our device better, thank you sir. This will remain relevant for me until the official AOSPA rolls out a new version.
[OnePlus 2 Android Development] nicesoni_ash:
I noticed today that if you disable it going through the menu option, it will happen but if you disable your hardware keys through qs, it doesn't happen.
[OnePlus 2 Android Development] Mohit31:
Mother of observation :good:

Tried it and noticed the same

Really a weird bug:eek:
[OnePlus 2 Android Development] Mohit31:
Just curious, can this help us figure out the problem and hopefully solve it..?

Or it doesn't help much..?
[OnePlus 2 Android Development] nicesoni_ash:
It should. Since both methods do the same thing, both have different implementation so replacing the bad one with the correct one should fix it. I'll try to have a look at the source code tomorrow and see if if I could find anything interesting. Not too good in java though but still hopefully old c++ days may help.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[OnePlus 2 Android Development] :
[MENTION=4443334]Grarak[/MENTION] has fixed it (hardware & on-screen clash) in the kernel. His CM14 build (on twitter) has the fix. Do folks absolutely want it on CM13?
[OnePlus 2 Android Development] Mohit31:
If its not that complicated and will take less time and efforts to implement it in cm13 then I don't mind :p

Otherwise, no.
[OnePlus 2 Android Development] nicesoni_ash:
Any link to the commit/s?
[OnePlus 2 Android Development] :
https://github.com/Grarak/android_k...mmit/668e6b4864088e166047654a267880487fa4f374
[OnePlus 2 Android Development] nicesoni_ash:
Need to read what it's doing actually and hopefully then will merge tomorrow. Thanks again.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.

Edit:

Build is going on.. Will see tomorrow how it's pan out. Good night for now.