yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] piet8stevens:
Marshmellow

Not sure whether we are allowed to ask this on XDA, so if not, just ignore: will it be possible to bring out a XenonHD version based on Marshmellow? HTC will not bring out anything for the m7 and I do not know enough about drivers etc... to understand whether it is possible for the XenonHD or CM teams to keep porting newer releases to older devices.

Thank you,

Piet
[One (M7) Original Android Development] maritimesbob:
Nice rom. So far so good.

Tried installing the following theme, but it hangs up on "installing"

https://play.google.com/store/apps/details?id=alter.MIUIv6Light&hl=en_GB

It seems some themes will install, but some will not. Is this normal for a layers rom or one that is in the early stages such as this?

Thanks,
[One (M7) Original Android Development] ljjehl:
If you have any layers theme questions, I really suggest asking the themer, or in the layers community. It's possible some layers themes are not setup properly to the latest RRO specs. Check here:

https://plus.google.com/u/0/communities/102261717366580091389
[One (M7) Original Android Development] ljjehl:
We are planning to move to the next version when this time comes. At this time, source is not ready for Non-nexus devices, just yet.
[One (M7) Original Android Development] kemihansome:
Todays update bootlooping....
[One (M7) Original Android Development] piet8stevens:
Not bootlooping on mine...
[One (M7) Original Android Development] mcduffie2010:
No neither bootloops at this place. All working like a charm.
[One (M7) Original Android Development] ljjehl:
Did you forget to fastboot flash boot boot.img...edit: disregard, not m7 specific, I was thinking my other device thread. Need coffee...
[One (M7) Original Android Development] ljjehl:
I take it that the version in post #2 is working for you guys? As far as MMS and radio/data usability?

Edit: whoops, wrong thread. Had issues prior in oneX thread, please disregard, lol.
[One (M7) Original Android Development] OneCheekyDevil:
D00d, take a holiday.

You're confusing all the threads and going to confuse the n00bs. Next you'll think this is the crApple help thread :P
[One (M7) Original Android Development] IMTLD:
Everything was working fine and I wanted to try a sound mode, I did a Nandroid backup and flashed the mode, the phone did not boot so I wiped system\data\cache and tried to restore the Nandroid backup but I get the error 255 while restoring the data, any help would be very appreciated

After trying to understand the the recovery log it seems that the problem is from the file

/data//data/com.facebook.katana/databases/qe_db

I tried to delete it but could not neither from recovery not from cmd.

Edit: the data restoring worked after I copied the file data.ext4.win and then opened it with 7-Zip and deleted the folder

/data/data/com.facebook.katana/databases/qe_db

But still however I try to delete that folder from my phone it does not work, so I should do the same for any data backup.

I tried to use terminal and force delete(rm -rf) but I get operation not permitted
[One (M7) Original Android Development] ljjehl:
If you did a nandroid backup, then you can simply use advanced wipe and wipe everything but internal storage the nandroid backup should restore all back. Your trying to restore a backup on top of a build that's still there.
[One (M7) Original Android Development] IMTLD:
This is not the problem, the problem locates in this file

/data/data/com.facebook.katana/databases/qe_db >>> the file in not in the internal storage it is the the root directory /

When I make a nandroid data backup this file gets automatically backed up and once I try to restore the data backup this file fails the process

The problem is whatever I try I cannot delete this file, any ideas?
[One (M7) Original Android Development] 91ludesit:
I'm using the 9/4 build still, but I'm getting a lot of apps killed in the background. Like hangouts isn't delivering messages until I open the app and Plex gets killed while I'm watching a video.
[One (M7) Original Android Development] ljjehl:
Android can only have so many apps open.....
[One (M7) Original Android Development] 91ludesit:
Well it just seems like it's being more aggressive about killing processes than it was before.
[One (M7) Original Android Development] ljjehl:
If so, use kernel Adiutor to adjust the processes. (Low memory killer)
[One (M7) Original Android Development] 91ludesit:
It goes from light to aggressive, my guess is I'd want light?
[One (M7) Original Android Development] ljjehl:
I tried medium, but you can test it out
[One (M7) Original Android Development] IMTLD:
I noticed a problem in the recent apps menu, when I leave an app with the back key it does not appear in the recent apps menu and the close all does not appear wherever I put it>?
[One (M7) Original Android Development] ljjehl:
Are you in slim recents or normal recents?
[One (M7) Original Android Development] IMTLD:
Normal, Slim works well
[One (M7) Original Android Development] ljjehl:
Toggle clear all recents button. It seems to be a recurring issues that seems to be not fixed yet. Button shows up after a toggle off and back on
[One (M7) Original Android Development] mitchst2:
I can confirm that.

Might be best set to off by default.
[One (M7) Original Android Development] Alaadragonfire:
Hello , my proximity sensor is not working again , all of a sudden it stopped working after it was working fine with latest update , is it possible to have a flushable zip file with the fix.

I tried to dirty flash but it didn't work :/
[One (M7) Original Android Development] piet8stevens:
Slim recents - clear all & pinning

I also see no clear all in slim recents, not even after toggling on/off. I also see no possibility to pin a screen from slim recents.
[One (M7) Original Android Development] mcduffie2010:
Got the same problem
[One (M7) Original Android Development] SWisaiahAG:
+1

Sometimes upon connection to a call phone software reboots. But that could be layer thence related.
[One (M7) Original Android Development] ljjehl:
Slim recents only clear all with a pinch gesture.

As for prox sensor, not sure yet what underlying issue you have that caused it. Mine still works just fine. Maybe added layers issue with dialer theme?
[One (M7) Original Android Development] piet8stevens:
Thank you. Pinching does work. How about pinnin an app?

On another topic: with android pay rolling out in the US, does this work with XenonHD?
[One (M7) Original Android Development] ljjehl:
There's an option for pinning a screen in settings/security. I have never used it though.

Android pay should work if its an apk from Google Play. Youll just have to try it out when it come out
[One (M7) Original Android Development] ljjehl:
Just checked, Google Wallet will become Android Pay soon
[One (M7) Original Android Development] mcduffie2010:
Got my first OTA
[One (M7) Original Android Development] piet8stevens:
Me too.

2 questions:

a. How do we know what it does? (Changelog?)

b. Do we just dirty flash it? Do we need to re-flash gapps, xposed etc...?
[One (M7) Original Android Development] mcduffie2010:
I was looking for changelog too. Haven't found it.

I dirty flashed without a problem and no Gapps needed. Xposed has to be flashed again (I did it right after the Rom Flash without booting it up first)
[One (M7) Original Android Development] ljjehl:
Changelog is in Settings, About Phone

You can also read basic changelog for all devices in our G+ page, which is in post 2
[One (M7) Original Android Development] piet8stevens:
Yes, that worked with dirty flash and xposed. Then reloaded layers. Had to clear cache for a few apps but nice. Thank you.

I also found the changelog. Not really human readable. How can I find what the most important changes are?
[One (M7) Original Android Development] ljjehl:
A lot are just minor improvements, background processes.
[One (M7) Original Android Development] piet8stevens:
Reverse USB Tethering?

In one of the sense based ROMs, there was reverse USB tethering built in. Very handy. Used the laptop wifi to connect to internet and then the phone hotspot to connect my other devices to internet via the laptop internet connection over the usb between phone and laptop.

I just cannot figure out how to do this on this ROM. Is it possible?

Thank you,

Piet
[One (M7) Original Android Development] ljjehl:
Not sure if I have this or not. I do have USB tethering and I know it connects to PC properly. Thats Settings, Wireless and Networks section-More, Tethering and portable Hotspot.

This is where all the tethering is at...
[One (M7) Original Android Development] piet8stevens:
Thank you for the fast reply.

Yes, but all that does is make my phone connection available to the laptop so that it can connect to the internet via my phone data plan. What I need is the reverse, i.e., the phone being able to use the laptop internet connection.
[One (M7) Original Android Development] ljjehl:
http://xdaforums.com/showthread.php?t=2287494

There may also be apps in Gplay that does the same
[One (M7) Original Android Development] piet8stevens:
Black screen after long phone call + need to re-enter PIN

When I have a long phone call and hang up, I get a black screen and need to re-enter my PIN. I have tried some build prop changes to reduce the black screen, which seems to have the desired effect for short calls. But how to prevent my phone from requiring me to re-enter my PIN after a long call?

Thank you,

Piet

---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------

Thank you for this. I had already found that XDA thread and am trying to get it to work.
[One (M7) Original Android Development] ljjehl:
You'll have to give me more information:

Xposed?

you have pin lock enabled in settings/security/SIM card lock ?

also need to know what version of rom you have (check about phone in settings)

If it's possible, I could use a logcat of the issue.
[One (M7) Original Android Development] piet8stevens:
Sorry:

Yes, Xposed with Gravitybox etc... .

Pin lock enabled in settings/security/screen lock (not SIM card lock).

ROM version: your latest: XenonHD-09-13-15 (note: I think I have had this with the two prior versions, too; I did not have older than those installed).

Will PM you a logcat.

Thank you for all your help. I thoroughly enjoy the ROM.
[One (M7) Original Android Development] ljjehl:
You might want to look at the settings on any of the mods in xposed.. I have 2 users that use pin lock and have no issues. Xposed not in their setup. Maybe you can test a version without xposed , just to eliminate one scenario.
[One (M7) Original Android Development] piet8stevens:
I have a feeling it has to do with the proximity sensor. My phone screen stays on during a call. It therefore does not see I am on a call and requires me to re-enter the PIN after 10' of inactivity, which is what I have set as the auto-logoff delay. I have disabled all modules in xposed. Then, the first time, the screen does turn off when I make a call. But not the subsequent times. So, the proximity sensor itself seems to work, but not sure what causes this behavior. I tried setting gsm.proximity.enable = true in build prop, but that does not have a discernable effect.
[One (M7) Original Android Development] ljjehl:
You need to eliminate Xposed altogether to test, just turning off modules alone won't do it, adding Xposed and modules already made those changes in system
[One (M7) Original Android Development] piet8stevens:
Thank you. I uninstalled xposed and yes, proximity sensor now works.

So, problem is not in XenonHD. I will try and find a solution somewhere else on XDA.
[One (M7) Original Android Development] piet8stevens:
Well, it seems it is not as simple as that. I tried to install xposed and re-add the modules one by one to find out what causes the problem. I did something wrong so that all my modules were added at once. So, I re-deleted xposed (both the app and I used the xposed uninstall zip) and now the proximity sensor still does not work. I will continue to investigate and report back.
[One (M7) Original Android Development] piet8stevens:
OK. I have now restored GPE5.1+ from santod040 (my previous rom). I can confirm that the proximity sensor there works, with xposed and all my modules active. So, there must be something with XenonHD and the proximity sensor on my M7 independent of xposed.
[One (M7) Original Android Development] ljjehl:
There is a difference here. Xposed does not play nice with AOSP based roms, due to the tweaks involved in the rom. Xposed is better suited to GPE based roms, since they are inherently stock.. End of story. That's why I don't support using Xposed, since it messes up all the tweaks that are added. Nothing wrong with XenonHD, everything wrong with Xposed. Try adding Xposed to CM, AICP, and other AOSP based roms, you'll have the same issues.
[One (M7) Original Android Development] piet8stevens:
OK. But I still have the proximity problem without xposed. I will do a clean install of XenonHD to confirm this. I do not mean to detract from XenonHD. I am just trying to use it and I enjoy using it.
[One (M7) Original Android Development] theslam08:
Yeah usually best testing practices (and for reporting problems) is to have a control, then the experiment. So that means,

Install with full wipe (dalvik/cache/data/system) then try to see if problem is there (for you: see if proximity sensor is working)

Then after testing [out-of-box] version, try adding mods (xposed) to see if problem does or doesn't persist.

If problem persists after xposed, you know it is that. If it happens on a clean install, then you know it is xenon. This way you can report properly. Either letting the dev know their stock ROM has the bug, or it doesn't. And if it doesn't, then you can let the community know, with xposed installed problems arise. If it does it from stock, try running a logcat during phone call and testing the sensor. Also there are proximity apps you can test with.

This way you can save time for everyone including yourself.
[One (M7) Original Android Development] piet8stevens:
Proximity Sensor not working

OK, thank you for the advice. Sorry for too many posts.

I have spent a couple of hours experimenting and am finally close to the source of the problem.

1. Clean install of XenonHD -> no problem with proximity sensor. I did a full wipe and installed the latest version (OTA; XenonHD-09-20-15).

2. Added all my apps and nova launcher with Titanium Backup (note: I did NOT install xposed app or zip). No issue, proximity sensor still working.

3. I ran tasker. My tasker setup is not very clean and results in some error messages. Now, the proximity sensor no longer works. I confirmed that this is really the issue by doing a nandroid restore and repeating steps 2 and 3. After first tasker run (just starting it, really), proximity sensor stops working.

Note: with this tasker setup (and also xposed), the proximity sensor on a GPE5.1 rom works.

Next steps: figure out which portion of my tasker scripts creates the issue. Will do that in the next few days. But maybe someone else can throw light on this?

-------------------------------------------------------------------------------------------------------------------

Edit: OK, I found it. I had an action that triggered on proximity sensor which then made the screen dark. When I disable that trigger, everything is OK again. Not clear why this does not do anything on the GPE5.1 ROM. So, sorry to have wasted all your time: it is not related to XenonHD or to xposed. There is a difference in how this script works between XenonHD and GPE5.1. Case closed.
[One (M7) Original Android Development] akki4play:
Is there any Fm Radio application available for this ROM..?
[One (M7) Original Android Development] tornido067:
Is there any custom kernel to flash with this rom ???
[One (M7) Original Android Development] yellowrose75:
Hi

I am having a problem with this rom. Everything else works smoothly but when I lock the screen upon trying to wake the device only the buttons lit up and I can see nothing on the screen. The phone keeps working but screen remains black.

Please Help

I am using HTC ONE M7 International version S-On
[One (M7) Original Android Development] ljjehl:
Need more info. Date of rom (from About Phone), and modifications added after rom flash (ie. Xposed and mods, version of Gapps, etc.) A logcat of the issue would be nice. Do you fastboot flash the boot.img after every rom update?
[One (M7) Original Android Development] ljjehl:
I do not know. I do know OEMs have stopped including the FM radio chip in their devices, so Google has pretty much did the same for AOSP builds. If there are some current devices that have it, I dont know it.
[One (M7) Original Android Development] ljjehl:
The kernel in this rom is already slightly modified. You can use the kernel app in Settings to tweak it some more. If you want a different M7 kernel, you'll have to search XDA.
[One (M7) Original Android Development] yellowrose75:
Thanks for your reply.

ROM : update-XenonHD-09-06-15-signed-m7.zip

GAPPS : tk_gapps-modular-pico-5.1.1-20150920-signed.zip

Yes I Flashed boot.img (Thats why it even boots doesn't it ??)

NO Modifications at all not even a single app install

LOGCAT (I dont know how to + The ROM is unusable in this state and I have only this phone :( But if needed must then will do something)
[One (M7) Original Android Development] ljjehl:
Well, your footer showed you were s-on. In that case, you have to fastboot flash boot.img always. Sometimes it's not needed if there were no kernel updates, though. If you were s-offed, you can simply flash rom in recovery and that would be it.
[One (M7) Original Android Development] mcduffie2010:
I'm S-on and don't flash boot img. Everything works smoothly.
[One (M7) Original Android Development] ljjehl:
I dont see how Boot.img could flash to s-on partition without using fastboot or Flashify. Does Tap2Wake work for you??
[One (M7) Original Android Development] mcduffie2010:
Yes it does fluently
[One (M7) Original Android Development] piet8stevens:
OTA - how to decide whether to update or not?

Hi, I am very happy with this ROM and I use it on a daily basis. Have been using it for more than 1 month, coming from GPE (and sense - Insertcoin - before that). Basis for my interest is speed, customizations, layers, rapid fixing of issues such as stagefright and probability that we will get Android M via XenonHD. I do still struggle a bit with phone getting quite warm, but am working on that. Am a bit worried about the google pay discussion (google pay not working on custom roms), but this is not an issue for me right now as google pay is not available in this country, yet.

Question: how to decide whether to install the latest OTA or not. The changelog is difficult to read for me. Sometimes, an update breaks something that used to work. Sometimes, an update fixes something that was broken. But, as far as I can tell, when using the previous OTA (Sept 20), my phone works fine. So, in summary, applying the latest update seems to have more downside than upside.

It is also difficult to know which changelog to read on the web-site. In settings\about, I can see the changelog relevant to this update, but only after having installed the latest OTA.

So, is it a question of trial and error or has anyone found a system, like waiting for a week or so before applying this OTA?

Thx,

Piet
[One (M7) Original Android Development] genseng:
I've not had any issue with things breaking in recent updates from Xenon. There was the time he forgot to pack Kernel Adiutor but it was easy to install from the store. That said, my battery performance did suffer the last week with the 9/20 weekly which I assume is due to dirty flashing several weeks in a row. I've done a clean flash today. To soon to say if it helped but I'd be surprised if it doesn't. You should always do a backup of its going to be inconvenient to clean install when dirty flashing doesn't work out.

For the record I use Xposed with Amplify and Greenify modules and don't seem to have any obvious issues.
[One (M7) Original Android Development] tornido067:
guys is there any sound mod that can be used with XENON rom ?
[One (M7) Original Android Development] yellowrose75:
Sorry for late reply I had internet problem. I do flash the boot image through fastboot every time I flash a new rom. But still the same issue I haven't installed a single app in the rom, tried factory reset even tried without flashing gapps still the same issue. When I lock the screen upon unlock the buttons lit up but the screen stays blank. I tried another thing i.e. I used DROID@SCREEN to see if the phone is working and it shows a perfectly working phone. It shows the screen on PC but the phone screen remains blank.

Any Ideaaasss plzzzzzz ?
[One (M7) Original Android Development] ljjehl:
Just from what you describe on viewing your screen on the PC, sounds like a broken screen or cable. Possibly a cable got loose. Its kinda strange on why its dark, seems to be a physical issue.

Edit: Try this method. http://forums.androidcentral.com/t-htc-one/362411-htc-one-black-screen.html#post4385895 might be your fix.
[One (M7) Original Android Development] yellowrose75:
How can screen be broken? I am using the phone fine on stock sense based roms. At present I am using NusenseSix rom for the past 3 months without any problem. I have also used Viper Rom as well.

The link you suggested I have checked that out prior to posting my problem here. That didn't work for me. :(

I repeat again that I have got no problem when using sense based roms. The problem only occurs when using AOSP roms like Carbon, Xenon, Slim etc. And as I am S-on therefore I cant try Kitkat :(

Thanks for time
[One (M7) Original Android Development] commencal661:
Have you tried manually flashing boot.img that's in the ROM after you flashed the ROM?
[One (M7) Original Android Development] yellowrose75:
Yes I always do as I am S-on
[One (M7) Original Android Development] ljjehl:
What is your bootloader version? In addition, what recovery are you using and what version?
[One (M7) Original Android Development] steinsgateislove:
Very good ROM but calls are randomly disconnecting :/
[One (M7) Original Android Development] ljjehl:
I don't seem to have this issue. May be your carrier signal
[One (M7) Original Android Development] steinsgateislove:
I don't have this problem on any other ROMs. Also ironically i have better mobile signal on this rom than on others. Maybe i need to clean install update becouse i kept dirty flashing updates for quite some time :o
[One (M7) Original Android Development] ljjehl:
Backup first. Sometimes its better to clean house. Ibdid that 2 versions ago
[One (M7) Original Android Development] yellowrose75:
Hboot 1.61.0000

TWRP 2.8.7.0
[One (M7) Original Android Development] rongold3:
Fahrenheit to celsius

I got Fahrenheit degrees on: Lockscreen and statusbar.

I went through the settings but couldn't find a way to change it to celsius.

Any ideas?
[One (M7) Original Android Development] green0153:
Settings, ROM settings, cLock settings and there you have Use metric switch

---------- Post added at 01:25 AM ---------- Previous post was at 01:24 AM ----------

Can i turn off The setting that wakes up The phone when i touch it or take it in The hand?
[One (M7) Original Android Development] mysdim:
Good morning,

I'm unable to install the update of the Layers Manager from Play Store. Error code 505.

Thanks
[One (M7) Original Android Development] psychology:
Uninstall and reinstall
[One (M7) Original Android Development] mysdim:
Good idea, but it is not possible to uninstall the Layers Manager. In Play Store the options are 'open' and 'update', in the app drawer it's also not possible.
[One (M7) Original Android Development] ljjehl:
you can remove the app via es file explorer, root explorer or similar:

http://www.addictivetips.com/mobile/how-to-remove-uninstall-android-system-apps/

After that, you can download and install newest layers app
[One (M7) Original Android Development] mysdim:
Ok, so that it is a normal behavior at the moment and no problem. But I think you will update Layers Manager with the next OTA, right?