yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] fireattack:
Wow, everything makes sense now. It also explains why my Nexus 7 2013 (I lied when I said I don't have any Nexus device, I meant any Nexus phone) is still using old launcher by default while my friend's Nexus 9 has Google Now Launcher by default. Thanks again
[One (M7) Android Development] blurhns:
anyone has very bad snapchat performance on the latest gpe stock?

like, putting filters is laggy as hell,sometimes even crashing the device.

in camcoder laggs baddly, like 2 secs 1 frame.

i'm not sure if it's a rom problem but before the latest update it was working fine. (of rom,not snapchat)
[One (M7) Android Development] majed19:
Snapchat never worked properly for me on any non-sense based roms :)
[One (M7) Android Development] zzieluuu:
Someone can help me with camera on this ROM ? Snapchat video recording really sucks and lagging...not only on snapchat but on every 3rd apps using camera like Messenger etc.
[One (M7) Android Development] fenstre:
Anybody have a link to the *real* stock 5.1 GPE?

I installed the stock 5.1 rom linked in the OP, but found it's not actually stock--it's badly rooted, so it has serious permission errors. For example, adb shell cannot access /sdcard. This is not an Android bug, since an unrooted system does not have this problem. (Nor does a system that has been rooted with SuperSU or TWRP).

I really need ADB to work. Can anyone tell me where to get a stock flashable GPE .zip of the new Android 5.1? [MENTION=1331268]santod040[/MENTION], I don't suppose you made any less modified .zip?
[One (M7) Android Development] fenstre:
Also, does this file crash your phone?

I found any video encoded with ffmpeg color levels filtering crashes my phone! Does this happen to you, too? :D

It happened both pre- and post-upgrade. (Both versions are 5.1, "stock-ish".) Just put the file in /sdcard and try to view it. Immediate crash for me, every time. Give it a try! It's a small file. This seems like a serious Android bug, but it could just be that something's wrong with my phone. (I had to attach it as a .zip, but the file should be unzipped when you test it.)

Edit: I found out it's a bug in HTC's video drivers. I can't find the link, but someone else here on XDA actually patched the kernel for his m7, but I don't know whether he submitted a bug, and I assume HTC isn't going to fix this unless someone exploits it to gain root or install malware.
[One (M7) Android Development] santod040:
You're highly confused and wrong.

It is stock, it simply applies SuperSu during install.

Adb works just fine for me, this has been discussed quite a lot in the thread.

If you have sd card issues, you should read as far as the second post of the thread...

Have a nice day.
[One (M7) Android Development] fenstre:
Yes, I may have been confused. I thought my last ROM (the prior 5.1) was one that you made, but I may have been wrong. One thing I can say for sure is that stock Android GPE does not have permission issues or SD card issues--none that I've ever seen, for any use case. (Besides the obvious fact that /sdcard is not a real filesystem.) Rooting does not create these issues. (I know this has been discussed in this thread--you and I have discussed it before, but I don't I communicated clearly enough..)

For your reference, I can tell you how a stock ROM works:

When you log in via ADB, the shell account is UID=2000 and has full permission to access /sdcard, but no elevated permissions: no /data/media, for instance. When you type "su" (if you've installed SuperSU), you become root with full expected access. However, "adb root" is not possible.

Whenever I've installed your ROMs (which I liked very much until Google implemented SELinux), things go very differently. Upon opening an ADB shell, the user has UID=0 but no permission to see any folder I tried, even /data/local/tmp. This means "adb pull" and "adb push" do not work. Typing "su" still opens a shell with full permissions as expected.

[MENTION=1331268]santod040[/MENTION], would you like to examine a nandroid dump that is rooted but has no SELinux problems? I would be happy to provide one if you'd like to see what the difference is. (Obviously it's the older version of 5.1.)
[One (M7) Android Development] santod040:
I know very well about how a rooted Rom works.

If you don't like how I've packaged it, then by all means, use a different one or make your own from the OTA.

This is directly made from the Update.zip which is the entire Rom.

There is nothing missing or different about it...

I am able to use adb with absolutely zero issues, so I don't think there's much I can say or do to satisfy your doubts or concerns.

I definitely do NOT need a nandroid backup of the previous Rom, as I already have one.

Yes, I do get a bit touchy when someone tells me I posted a poorly rooted Rom, as that's not even close to being true or accurate.

The updater script simply installs supersu from the actual supersu zip during install, so there's nothing more or different to be done here.
[One (M7) Android Development] fenstre:
Understood. I'm aware that as someone who knows "enough to be dangerous", I'm the most frustrating kind of user. Sorry about that. On the other hand, I know a bug when I see it. But you're saying that on your phone (even with SELinux, without running workaround hacks from post #2), adb shell opens with reasonable "user" permissions, and you can execute "adb shell ls /sdcard/" without error? If so, I'm way out of my depth.
[One (M7) Android Development] santod040:
Ummm, /sdcard usually is a symlink, which should be "followed" to the real place. (this is what the restorecon is about in post #2, using stock recovery all along you wouldn't need it)

Check with ls -l where it points to, which you will find is /storage/emulated/legacy

So then you do the following: yes you need su to access storage, this is Lollipop protection.

Don't blame me, blame Google and HTC.

adb shell
su
ls /storage/emulated/legacy

I just did it.

Yes it works!

Still doubt me, want a video for proof? :silly:[emoji14]

HERE:

If you need something more, then I probably can't help you, since everything I expect to work, works as intended.

I can't imagine 100% stock behaving any different, as HTC's installer script matched mine almost entirely from my previous version, and I've added what they did to it, in the last update as well.

Feel free to go back to stock and take the OTA yourself, if you think you're missing out on something by not doing so.

Want more freedom, and ability to adb push to /sdcard/ while booted into the OS? You will HAVE to set SElinux to Permissive Mode.

Drag and Drop is always easy if you just wanna drop files to internal sd/sdcard.

You can use adb push in Twrp as well, while still being set to Enforcing.

This is just the nature of Lollipop security.
[One (M7) Android Development] panos_ts:
Hello,

since GPE+ is still under construction, I'd like to report a bug that I found on the latest plus ROM. Whenever I try to change the the user's porfile pic (swipe down notification bar, top right corner) by choosing a pic from the gallery or by taking a pic from the camera, I get a "No SD card space" (or a similar error message, don't remember right now) and the profile pic isn't changed.
[One (M7) Android Development] santod040:
Use Google Photos not HTC Gallery.
[One (M7) Android Development] panos_ts:
Thanks for your quick reply,

I hadn't chosen (during installation of the ROM) the G photos app to be installed so I couldn't test it with it. Will do it though when the next version of GPE+ is up!
[One (M7) Android Development] santod040:
You can install it from the Play Store. :)

https://play.google.com/store/apps/details?id=com.google.android.apps.photos
[One (M7) Android Development] panos_ts:
To be honest, since the official update rolled out (and I messed my One by installing it) I switched to a LG G2 I have so I can't test it right now. And since I don't want to flash any other ROM to my One, I decided to patiently wait for your GPE+ ROM and then use the M7 again.
[One (M7) Android Development] monacoo:
What i ??
[One (M7) Android Development] adambala:
Hold it and you would see the I tap and hold
[One (M7) Android Development] kecodoc:
My devices run hot

Please help me download link stock kernel GPE 5.1

Thank
[One (M7) Android Development] biglo:
Can someone suggest a good app for exchange email for this rom? I tried gmail but I don't want to have gmail and exchange just exchange. I tried outlook and it just sucks now after so many updates. It's weird that the email apps made by the phone makers are the good ones.
[One (M7) Android Development] leo10messi:
Hey

I know this issue has been discussed earlier but the battery life on my M7 (GPE 5.1) is consumed most by Google Services. I dont use auto sync and my location settings is on battery saving. Is there any solution to this? or I have to deal with not so good battery life?

Otherwise, this is one of the best rom i have ever installed. Hands Down, that dark theme is so cool :D

P.S. I am coming from Stock Sense after stagefright update.
[One (M7) Android Development] LRNZ09:
On the latest GPE stock rom I have a huge battery drain too. On GSam Battery Monitor I can see that most of the battery is consumed by the kernel.. I'm really confused about this, since I'm using NuK3rn3l :confused:
[One (M7) Android Development] majed19:
U can try different kernels , or maybe wiping delvik and cache

Try using power nap, a module for xposed

Also try installing appops and disabling location services and keep awake for google services
[One (M7) Android Development] freduser:
I apologize up front for not searching as I'm at work but has anyone had issues with video freezing whether local or streaming on pretty much any video apps? Netflix, youtube and the local video players all freezing.

Also as an aside I'm seeing daily ui crashes.

I allowed the installer to do the recommended wipe prior to install.
[One (M7) Android Development] sesser:
lockscreen issue

Hi, many thanks for great peace of work, everything work great but im facing an annoying issue with incorect possition of statusbar on lockscreen...

i couldnt find any solution or at least similar problems in this rom topic
[One (M7) Android Development] djbspliff:
Has anyone actually tried using the new Android pay app, I get an error msg something to the sort say'n my card is not supported neither cc or dc. All this worked fine with wallet.
[One (M7) Android Development] lilbluemirage:
Read somewhere that Pay doesn't work on rooted devices.
[One (M7) Android Development] djbspliff:
Damn is that right. Anyone's else come across this issue. In addition I can't use my mic on the Google keyboard is that any relation to this rom. It didn't work on the last build which was my first lollipop rom it worked previously on KitKat rom
[One (M7) Android Development] santod040:
Mic works fine...

As for Android Pay, that has come up in almost every single rom thread on this forum and all over the web.

There are methods of working around it as well, which have also been widely discussed and works for many, but not everyone.

(basically unticking the enable superuser box in SuperSu)

More Info:

Google Security Engineer Explains Issues With Root and Android Pay in the XDA Forums
[One (M7) Android Development] xpurtwitness:
I've tested it out on both versions of the ROM from this thread. It did not work for me on the "Plus" edition, regardless of temp-unrooting, permanent unroot, locked or unlocked bootloader.

It did work when I flashed the "Stock" edition from this thread, with an unlocked bootloader, non-stock recovery (TWRP), and temp-unroot. You'll likely need to keep superuser disabled to add cards and use tap to pay, and enable it only when necessary, e.g., doing a backup with Titanium.
[One (M7) Android Development] leo10messi:
It didnt help

Google Services is sucking upto 20% of the Battery. I have never experienced such stats.

Is there anything else I can do?
[One (M7) Android Development] LRNZ09:
I've partially solved with ElementalX.. now it seems that "Cell standby" is usign a lot of battery... I really don't know what do, and searching on internet didn't lead me to an accurate answer :crying:
[One (M7) Android Development] 4Strings:
OK. So I pulled the trigger and flashed GPE+ 3.2, but no matter what I do, Dark GAPPS, and DARK keyboard do not work... I've tried a full wipe and a dirty flash over 3.00... No luck. :(
[One (M7) Android Development] majed19:
I don't know actually, did u try updating it ? Maybe u have an old version or something, it doesn't suck more than 1% in my case

It is most probably related to your service provider, or the signal in ur area is weak, try switching into 2g only when not using data

I am using the smart network feature from gravitybox it switch to 2g only when not active

Here is my stats using xceed kernel
[One (M7) Android Development] fenstre:
I'm sorry about my tone, really. I truly did misunderstand the situation--I thought packaging a ROM was an archive/conversion process, but you've helped me understand it's an authoring process. So I thought you get a stock system, maybe do stuff, then package it. But based on your comments, there is no ROM without "do stuff". The "do stuff" is how the ROM is made. So I thought you had done various optional things to a stock image to change it (besides installing SuperSU). Now I see that's not how it works at all.

Also, when I said /sdcard isn't a real filesystem, I meant that /storage/emulated/legacy is a bind mount of /data/media/0 with altered permissions and inability to set certain file metadata.

I did a bit of comparison and so far I found out that the last 3 lines of build.prop are not present in a stock build, and obviously adbd is running as a different user+context in the two builds. But that's not because of build.prop, as far as I can tell. My guess is that it's because of the difference between "production build" and "engineering build". That's how a lot of quality software works. Two versions, made from the same source. BTW, here's how permissions look on the system from RUU+OTA:

$ adb shell
shell@m7:/ $ ls /sdcard/ >/dev/null && echo success
success
shell@m7:/ $ getenforce
Enforcing
shell@m7:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[One (M7) Android Development] Coolgoly:
Try to delete all data of google play services app and restart your phone.
[One (M7) Android Development] MrCrunch:
No problems with the dark options on my side.

HTC M7 GSM, wiped system,data,cache,dalvik before flashing (so basically everythig except internal storage).

Did you check the md5 after downloading? Maybe got a bad download?
[One (M7) Android Development] Macrusin:
I have accidentally installed the update notification. (650MB)

Now my phone is stucking during rebooting.

Any solution?
[One (M7) Android Development] santod040:
Wipe

Flash rom from OP or restore backup you made before doing that...[emoji12]
[One (M7) Android Development] kRYySTy:
hi! i have currently htc one sense, with the latest sense firmware. Can i install this rom without installing GPE firmware? Anyway if u recommend using GPE firmware i can do that because i have s-off
[One (M7) Android Development] santod040:
Lollipop Sense firmware is fine, no need to flash GPE firmware. [emoji106]
[One (M7) Android Development] notherman10:
Hey,

I just flashed the plus version, and everything is working great so far except for a couple of things:

1. When I wake up the phone, it takes 4 seconds to open the screen. This is annoying when trying to see the time or something.

2. Video recording in Snapchat is extremely laggy.

Are these just problems with me or is there something wrong universally?

Thanks,

N
[One (M7) Android Development] santod040:
Snapchat is just buggy, in my opinion.

As for number one, read the note in the OP, right below the download link you had to have clicked on...
[One (M7) Android Development] notherman10:
Ah yes I'm so sorry, just didn't quite get what ambient mode is. Is there a way to disable it after flashing?
[One (M7) Android Development] santod040:
Yes

Settings > Display
[One (M7) Android Development] tornido067:
feeling sad :(

this rom is really fast and stable..just battery drain :( why do i have this huge battery drain :(
[One (M7) Android Development] notherman10:
Thanks :D

Sorry for my noobiness, I'm really out of touch with these, been in the iOS JB scene for too long it seems...
[One (M7) Android Development] tim071286:
MailWise
[One (M7) Android Development] Sinistersky:
Battery drain? By what? How long does the battery last?
[One (M7) Android Development] tornido067:
i dont know but i guess it is the play services..my battery last only 2 or 3 hours :*(
[One (M7) Android Development] Sinistersky:
That is really bad. My guess is it is a hardware problem, not the ROM?
[One (M7) Android Development] biglo:
Thanks I will probably purchase it and see how it works out.
[One (M7) Android Development] weigeloveu1:
does this rom support f2fs？
[One (M7) Android Development] darryl_p:
Never had so good battery life. Nothing wrong with the plus version. I'm getting over 3 hours screen time with normal use sometimes 4 hours.
[One (M7) Android Development] dar87:
That's not possible. my phone has gotten better battery life after flashing this rom. Check if it's a hardware.

Use GSam battery monitor and see if it's Android Kernel that's draining battery...If that's the case you need to go to your recovery and clear cache/dalvik.

Sometimes it can be Google services as they are the main reason I want to leave android for iOS. Google services is the price you pay for using an Android with Google Play store installed.

The last reason could be your battery has depreciated, and repairing the unibody phone is pretty much not advisable.
[One (M7) Android Development] FaYVeS:
santod040

Hello. Can you find out how soon will the new version GPE +?

I'd like to be removed from the shutter unneeded tiles, dimmer and so on.
[One (M7) Android Development] sorinake13:
no eta !!! Read the xda rules !!!
[One (M7) Android Development] tinyturtles:
Bootloops

I've had some pretty great experiences with the GPE+ ROM except for one thing. When I go wipe cache/dalvik through TWRP, I get a bootloop and have to reflash the ROM in order to get back into the system. I think it might be a problem with Xposed. I installed the version present in AROMA settings and not the latest version of Xposed. That, plus Gravitybox. Does anyone else have bootloops after checking those two options while installing the ROM? I've checked and even if I choose not to install Xposed/Gravitybox, I still get bootloops (I've waited for up to an hour to make sure I wasn't just being impatient) after wiping cache/dalvik. Any thoughts on what could be going wrong?
[One (M7) Android Development] b-jack:
Theres a new update today via OTA, installing right now, will be reporting
[One (M7) Android Development] santod040:
Newer then h9, or are you just getting up to speed? :)
[One (M7) Android Development] b-jack:
No bootloops or whatsoever for me, and I did installed both Xposed and Gravity box. when you were installing GPE did you wipe data/dalvik/cache/system ? Do those and report back here.

---------- Post added at 12:27 AM ---------- Previous post was at 12:24 AM ----------

Idk, whats the latest rom so far, I didnt really see the build number when the update comes up, I was too excited. :D
[One (M7) Android Development] santod040:
Probably the 6.04.1700.9 CL536258 update which has been in the OP a couple weeks now. ;)
[One (M7) Android Development] b-jack:
Whaaaa... I have been using this rom for like 2 weeks, and the update just popped out now ? lol , anyway getting error while flashing, "E: error command (firmware)" , i think im having bootloop but i'll give it a minute just to make sure :eek:
[One (M7) Android Development] santod040:
You can't install a stock OTA using Twrp, it will certainly fail at the firmware part...and definitely don't wanna apply that on top of the G+ rom.

If you want the latest stock update with root, download it from the OP.

Otherwise you need a stock recovery and a fully stock system to update via OTA.

Might even be worthwhile to read back from the time I posted the update on the 17th up till now.
[One (M7) Android Development] b-jack:
So no flashing OTA through TWRP ? and don't flash the OTA on top of G+ rom ? so this OTA is only for Stock rom yes ?
[One (M7) Android Development] santod040:
Yes, it's a stock OTA from Google/HTC which is what the updated stock rom in the OP is, only rooted and Twrp flashable.

It's not an OTA from me... I post Twrp flashable roms to make it simple to update.
[One (M7) Android Development] b-jack:
So basically this OTA just popped out for everyone else (both stock and G+), 650mb in size and anyone on G+ who got overly excited (like me) who flashed it will get bootloops. Theres no way to prevent this from happening ?
[One (M7) Android Development] santod040:
There were users on stock that took it, it failed at the last firmware part, but still booted.

But you should never download and flash a stock OTA while running a custom Rom and recovery, Rom flashing 101...

You simply disable notifications for the update as has been mentioned and carry on, or flash the updated rooted Rom I posted the day after it came out...
[One (M7) Android Development] b-jack:
This is why people read op *facepalm* lol, thanks anyway, this ROM is great ! Will be my daily ROM bc stock cm12.1 drains battery like ****. :(
[One (M7) Android Development] tinyturtles:
yes, wiped all of those (data/system/cache/dalvik) when I was installing the ROM. I tried it again just now (making sure to re-flash boot.img since I am s-on) and was able to reproduce the issue. Could being S-on have anything to do with it?
[One (M7) Android Development] b-jack:
I am S-ON too, but I managed to boot this rom and its working flawlessly (except when I accidentally flashed stock update with G+ ROM) are yours carrier version like sprint/verizon or something ?
[One (M7) Android Development] tinyturtles:
I'm AT&T but I am still using this version since (as far as I've always known) AT&T uses the same as global version. So, definitely not using the Verizon/Sprint versions. I've only downloaded from this thread.

Just now, while my phone was bootlooping, I unplugged it from the charger and turned it off and on again. Somehow that allowed it to start re-building the cache. Maybe charging the phone when it doesn't have cache built is causing problems...
[One (M7) Android Development] b-jack:
I don't think its that, sometimes when flashing cm-based rom, when I'm having bootloop, I just hard reset it (when the navigation light starts to blinking) it will boot the rom.
[One (M7) Android Development] tinyturtles:
Tried that... it will sometimes work but usually will not. Strange.
[One (M7) Android Development] b-jack:
Did your phone booted ?
[One (M7) Android Development] tinyturtles:
Ive got it up and running for now after disconnecting from the power outlet. Once the phone gets to 100% I'm going to try wiping cache/dalvik again and see if I can find a correlation between being connected to the power outlet and my bootloop issues. Thanks for all your help! :)
[One (M7) Android Development] xunqren:
any news about the new GPE+? can't wait to flash it! NEXUS 5X on the way ~~~~~~~~
[One (M7) Android Development] b-jack:
I dont think I am much of a help, but congrats in having your phone back up and running :D
[One (M7) Android Development] poondog:
Bump, anyone else with this issue or have a fix?

I am using 100% stock GPE and face this issue also, so its not a rom issue

ty
[One (M7) Android Development] santod040:
Saw a user with this on another device. Stock recovery factory reset was the only solution I've seen.

I know Twrp format of internal has caused some systemUI issues on multiple HTC devices since LP.