yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] 00bofh:
Lee - as always a smooth, fast ROM with _awesome_ battery life.

A few niggles I've noticed in TMoUS V8.0.0r72 (nothing earth shattering):

- Lookout (and other) anti-malware apps report that the code signing certificate for com.leedroid.framework has been reported as compromised and prompt to remove the "riskware".

- The battery charging function tops off the battery (usually overnight) and then sends toasts and pop-ups that "The battery is not charging, please try another cable or charger." Ummm, yeah, I hope that it stops charging once the battery is "full" <grin> I discovered this when the pop-up overrode my usual nighttime clock /alarm app and sent a bright white screen light through the bedroom ... at 3 a.m.

- When it goes to sleep, it _really_ goes to sleep. Radios get turned off, etc. (and no, I didn't set DnD mode). Once I wake the screen up after about an hour of "sleep", multiple "DINGS" for incoming mail, text messages, etc. and I have to manually restart Mobile Hotspot and trigger reconnects on any BlueTooth devices.

I don't spot anything blatant in the generic syslog, but if you can point me in the right direction I can gather up any log files or messages that might help figure out what's going on and send them along for study and review.

Thanks again for keeping the M9 in good kit!
[One (M9) Android Development] fhartane:
I know it has been mentioned before but I can't find any solution. I flashed r60 and couldn't find SuperSU anymore that appeared. Now I'm on r71 and it is he same thing. Can't even find the folder using ESExplorer. What's wrong ?

Envoyé de mon HTC One M9 en utilisant Tapatalk
[One (M9) Android Development] Halaster:
Flashed r47, got it all set up. Made a backup.

Did a dirty flash of r72. No SIM as expected.

Did a restore on the boot from my backup and it fixed the problem.

So using the boot from r47 backup on r72 works.
[One (M9) Android Development] Deathmeter:
Woo thats awesome news, ill do the same
[One (M9) Android Development] Halaster:
When you first boot with r72 after you have restored the r47 boot, it will look like you are having the no SIM problem, but it will go away in under a minute.
[One (M9) Android Development] Deathmeter:
good to know but haha im dumb and dont have a copy of R47 anymore. can i find it somewhere?
[One (M9) Android Development] Halaster:
Head to http://www.leedroid.co.uk/

Click SVN Guide.

For step 2, the checkout step, where it says "HEAD revision", change that to "Revision", and put 47 into the box.

Checkout r47 and follow the rest of the directions on the page.
[One (M9) Android Development] LeeDroid:
So it sounds like the superuser install is breaking the sprint boot.img .....

If this is the case then taking the boot.img from the svn and flashing it after the ROM should resolve the issue...

1.Drop the ROM zip and the boot.Img onto your device.

2.Flash the ROM and select no to the reboot prompt.

3.go to install and hit install image.

4.select the boot.img and select the boot partition in the prompt

5.reboot

Can one of you guys give that a bash? If it sorts it I can rearrange the installation
[One (M9) Android Development] LeeDroid:
Try my suggestion first, the root method changed between those revisions, that's probably the issue. In theory you shouldn't have and any issues with revisions 47-50
[One (M9) Android Development] Halaster:
Absolutely, ill try that now.

---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------

That did not work.

Installing the r72 boot.img broke it again, causing no SIM.

Switching back to my r47 boot.img fixed it. I will see if I can track down exactly which revision broke it now that I am aware that the problem is in the boot.img and do not have to replace everything.
[One (M9) Android Development] LeeDroid:
Can you send me the boot.img you are restoring please? Can take it apart and compare it
[One (M9) Android Development] Halaster:
So I just attempted replacing just the boot.img from 59, 54, 53, 50, 49, 48, and then 47, and all failed.

To get it to work again I have to do the restore of boot from my backup, not just the boot.img file pulled fresh from svn.

What is the difference between installing the boot.img and doing a restore of boot?

I have sent you over a link my TWRP boot backup.
[One (M9) Android Development] Deathmeter:
you have amazing internet lol, you download builds in like 5 seconds
[One (M9) Android Development] Halaster:
For those tests I was grabbing only the boot.img file. In "Checkout" you can click where it says "Choose items" and specify individual files you want to grab, instead of the entire recursive directory. :D At home I do have 150Mbps internet, but here at work its fairly slow.
[One (M9) Android Development] guidogsbn:
Hey, you woke up, :cool:Cinderella? Welcome, nice to see you here, mate! I will make my next step of rom hopping tomorrow and land here.
[One (M9) Android Development] LeeDroid:
Kernel up and running without a glitch! ?
[One (M9) Android Development] drmoeed:
Whoa ...

Great ...

Display driver calibration issue ??
[One (M9) Android Development] jeryx:
:eek::eek::eek: The pitbull is out of the box :D:thumbup:
[One (M9) Android Development] The Great Dane:
Yeah and it's working flawless[emoji12]
[One (M9) Android Development] Strangeland16:
What's new in the kernel buddy. Get my faulty m9 freplaced tomorrow and will be chucking this straight on again used first version from the start on old m9 and loved it will kernel give better battery ?
[One (M9) Android Development] The Great Dane:
It's very hard to say if it will increase battery life, only been on it for an hour. After a couple of days of use you can better judge for yourself.
[One (M9) Android Development] Strangeland16:
OK thanks can't wait to get my phone and get this up and running again
[One (M9) Android Development] brittoking:
Have you used the oqc kernel?? Is this comparable feature wise? I'm not trying to say one is better than the other just interested to see if you'd already run a custom kernel and noticed performance differences. Thanks for the help
[One (M9) Android Development] The Great Dane:
Haven't tried oqc kernel, only leedroid kernel as I test it before release. And you can't compare them as Leedroids kernel ain't released yet..
[One (M9) Android Development] brittoking:
Yea I realized that right after posting.. Thanks though
[One (M9) Android Development] itzsnookums:
Not yet anyways ?
[One (M9) Android Development] LeeDroid:
Totally stock at present with some debugging stripped.. I like to start off with a stock compile to make sure all is AOK before beginning to tweak
[One (M9) Android Development] LeeDroid:
LeeDrOiD HIMA Stock Kernel V1.0.0 - TEST

Here you go guys, let me know how you get on!

LeeDrOiD HIMA Stock Kernel V1.0.0 - TEST (MegaSync)

MD5# 4e182d714a25d8fad54ad5f4bb094b59
[One (M9) Android Development] drmoeed:
Working like a charm till now ...

No major issues ...

I've used both SkyDragon and OQC Kernel as well ...

Both have bug that touch screen doesn't work on Bootup unless you do lock/unlocke

... No issue in your Kernel ...

awesome work ...

P.S

Request for display driver caliberationl/ KCAL app ... :)
[One (M9) Android Development] twinnfamous:
Works great on my tmo-m9.

Thanks again for the great work.
[One (M9) Android Development] kangconsumer:
Where is the kernel source lee?
[One (M9) Android Development] beerente:
ROM and Kernel running smooth

Hi Lee,

Been a while since I used your ROM on the One X, glad you are back developing for the m9.

Within 15 min the phone was dropped off this Tuesday, I rooted and installed your ROM. Running without a problem.

Just installed the kernel, running smooth. :good:

Thanks a lot and keep up the good work.

Edwin
[One (M9) Android Development] billyjonstevens:
Thanks Lee will check this out, first time for me on your rom running great so far looking forward to the update.. Fantastic work
[One (M9) Android Development] guidogsbn:
Kernel runs smooth, temperature OK. Nice work, Sir!:good:
[One (M9) Android Development] Deathmeter:
either way man i just wanna say thanks for helping solve this sprint thing. i love this rom and if you and Lee can get it working that would be amazing
[One (M9) Android Development] Halaster:
I have full faith Lee and others will get it sorted out. It was a few days of testing to get it working initially in r47 as well, with multiple different fix attempts to sort it out.

Since there IS a working build, I am sure it will be possible to track down what changed between the working build and subsequent broken builds and revert the changes for Sprint, or fix them.
[One (M9) Android Development] raashnal:
Tmous SVN #72

:DI have been running this for about 24 hours now and it has been running great. It is charging quickly, holding its charge, sleeping like a rock but yet getting my messages & emails at timely intervals and is rock solid stable. What more can you ask for?? Thanks for all your work Lee.
[One (M9) Android Development] Mostafa Wael:
Well I have a 2 Mbps so even a 10 Mbps will be like heaven for me
[One (M9) Android Development] jbfountain:
Did you use the boot.img from the main svn or did you use the ones that are in the Sprint directory under extras-carriers-sprint?

Using XDA to unleash the power of Android on my HTC One M9 and S6 Edge Plus
[One (M9) Android Development] Halaster:
Ahh I used the main one. That explains that, tomorrow I will go through the boot.img files again to find out which one broke the support, pulling the correct one.
[One (M9) Android Development] LeeDroid:
My bad, I should have specified!..

Well pointed out [MENTION=6420972]jbfountain[/MENTION]
[One (M9) Android Development] jbfountain:
I have my moments. lol

Using XDA to unleash the power of Android on my HTC One M9 and S6 Edge Plus
[One (M9) Android Development] retiredtrebor:
I just noticed in the Sprint HTC M9 thread, that thicklizard posted a kernel. Would looking at it help figure out kernel issues with your rom?
[One (M9) Android Development] liam_davenport:
Yup on stock :D
[One (M9) Android Development] LeeDroid:
Finally, Friday is here!... woohoo! :)

So no issues other than the Sprint boot.img saga guys?
[One (M9) Android Development] Mostafa Wael:
According to me, no, until morning

Well first time my brother held my phone today, he wiped my data :crying:

Luckily I had a backup of MaximusHD (don't know how :laugh: )

And I had my phone back now, will reflash R72 when I am home
[One (M9) Android Development] LeeDroid:
Not sure you can accidentally factory reset a device lol
[One (M9) Android Development] Mostafa Wael:
I was in recovery mode about to flash EX

Then my brother held the device for me, I was in the laboratory

He kept messing up with TWRP settings

I came out to find my phone wiped and TWRP screen settings was altered

Thank you my brother :/
[One (M9) Android Development] cobrax2:
i've had yday the phone block on me with message: ussd code running after i tried to see how was my invoice. had to reboot

the sms notification on main lock screen sometimes is transparent, sometimes not

also the notification led still doesnt flash after a call in dnd mode and the notification of a missed call doesnt exist

thanks
[One (M9) Android Development] LeeDroid:
So the transparent notification is ambient display.

Not sure about it your DND issue as mine is fine, are you still blocking calls when in DND? You had the setting enabled last time, if it's blocked there won't be a notification or a flashing led mate
[One (M9) Android Development] cobrax2:
ok but why is it sometimes transparent and sometimes not?

no, i didn't have it enabled, it was unchecked, i replied then back :)

there is nothing that i want to block, i just want it to be silent lol

thanks
[One (M9) Android Development] LeeDroid:
It's standard MM behavior mate, takes a bit of getting your head around but nothing DND code wise has been modified.

The transparent version appears when the device is in low bit ambient mode, google ambient display or watch a video
[One (M9) Android Development] Mostafa Wael:
I see an R73 up now,

syncing and zipping will flash in an hour

I miss LeeDroid's battery life already :D
[One (M9) Android Development] aoryx:
Just rooted\flashed\leedoid'ed my new M9

man I missed ur roms since sensation( which is still running ur rom btw)

hope the problems u had then had been sorted out and glad to c u :)
[One (M9) Android Development] LeeDroid:
Life is on the up mate ;)

Welcome!
[One (M9) Android Development] Deathmeter:
Using that R47 restore boot thing I'm now rocking R73 flawlessly. So that's good, your kernel still doesn't support sprint yet right?
[One (M9) Android Development] Halaster:
I pulled down the r70 Sprint boot.img that still includes the tether fc fix you rolled back in r71, and tested your suggestion from yesterday.

I can confirm now that it works. I flashed it and everything is still working fine. :)
[One (M9) Android Development] LeeDroid:
Backup and try it mate, in theory it should work

https://www.dropbox.com/s/1wsre816t0ofuv3/LeeDrOiD_M9_Kernel_V8.0.3.zip?dl=0
[One (M9) Android Development] LeeDroid:
Dang... and superuser is ok? Sounds like its the superuser install that's been breaking it all along in that case, I will change the order in which it's flashed so it will work out of the box!

[MENTION=4165809]thicklizard[/MENTION] yours is pre-rooted, so I'm guessing re rooting a pre-rooted boot image was the issue. Do you have the 100% stock version?
[One (M9) Android Development] Deathmeter:
Nope, get no sim
[One (M9) Android Development] LeeDroid:
So a working build, restored boot.img - confirmed fully working.

Then a kernel flash, boot & sim issue is back?
[One (M9) Android Development] LeeDroid:
Changed the ordering of the flash as a temporary sprint workaround, all should be well now
[One (M9) Android Development] Halaster:
So after seeing Death was still having a problem and I was not it made no sense to me. It looks like the boot.img did not flash properly, which is why it was still working.

I flashed it a second time and SIM problem came back.

I then grabbed just the Sprint r47 boot.img and flashed that and it fixed the problem.

At this point I am back to finding out which release broke. I am going to test the boot.img files from versions that made changes.

Right now I am attempting "R57 LeeDrOiD Attempt to fix root & tether FC on Sprint & TMO-US". If this fails, ill try R56 and see if that works, isolating it to r57 breaking things.
[One (M9) Android Development] LeeDroid:
Try the version I have just pushed to the svn first mate, should be sorted, no need to flash the boot afterwards, just let it do it's thing
[One (M9) Android Development] cobrax2:
oh, ok, thanks
[One (M9) Android Development] Halaster:
So that does not work for me. I also tested a bunch of different boot.img files and here are the results.

r47 - Works

r57 - Works

r59 - No SIM

r70 - No SIM

r74 - No SIM
[One (M9) Android Development] LeeDroid:
Thanks for testing, that should help
[One (M9) Android Development] LeeDroid:
You said here R70 boot worked and then above that it didn't lol
[One (M9) Android Development] Halaster:
Ahh yeah, clarified that in an earlier post after. The boot.img had not flashed properly for some reason that time so that is why it kept working. When I reflashed it, it broke. I replied to someone other than you so probably missed it.

"So after seeing Death was still having a problem and I was not it made no sense to me. It looks like the boot.img did not flash properly, which is why it was still working.

I flashed it a second time and SIM problem came back."
[One (M9) Android Development] cobrax2:
r74 doesnt do full wipe

tried to clean install, twice (thought i did something wrong) selected full wipe, dalvik wipe, still my old screen and apps are there lol
[One (M9) Android Development] LeeDroid:
Are you s-off and which version of TWRP
[One (M9) Android Development] LeeDroid:
Think we have found it mate, I have a sneaking suspicion the LeeDrOiD kernel is being flashed!.. check the kernel version in settings when the sim error occurs, that should confirm it.
[One (M9) Android Development] Halaster:
Hey, I believe you are correct that it is the kernel that is a problem. Just ran the following:

First Test

Restored r47 boot backup.

Verified the SIM was detected and working.

Checked the kernel version:

3.10.84-perf-g3e32851

and@AABM #1

SMP PREEMPT

Second Test

I used "Install Image" on the r74 Sprint boot.img and rebooted.

Verified the SIM was not detected and a No SIM icon was present.

Checked the kernel version:

3.10.84-perf-g46bbed0

and@AABM #1

SMP PREEMPT

Third Test

Rebooted into recovery, still running the r74 Sprint boot.img.

Installed m9_(minimal_MM)_RC1A.zip kernel from Thicklizard and rebooted.

Verified the SIM was detected and working.

Checked the kernel version:

3.10.84Minimalistic

thicklizard@BadseedCustoms #38

SMP PREEMPT

Repeated the three tests above a second time to verify my findings. The kernel in r74 does not specifically state LeeDrOiD, but I am not sure if it is supposed to and replacing it with another kernel fixed the problem.
[One (M9) Android Development] LeeDroid:
Rebuilt the boot.img using the working backup you sent me.... head now at R75!

Rework updater & Aroma

Rework LeeDrOiD kernel installation (NEEDS TESTING ON SPRINT & TMO-US)

Fix Sprint boot.img & flash

Cleaned up T-Mobile US boot.img

Installer has totally changed, Sprint & T-Mobile US, feel free to try the in ROM custom kernel, I have left it as an option.... here is an updated standalone test zip, I have removed the cmdline modifications.

https://www.dropbox.com/s/1tsk9bwndlekn25/LeeDrOiD_M9_Kernel_V8.0.3-TEST.zip?dl=0

EDIT: the kernel will definitely not work on sprint for now, T-Mobile US still needs testing.
[One (M9) Android Development] Halaster:
Yep, just tested. Was about to say that this version works great with the default kernel, but the LeeDrOiD kernel is still not working on Sprint.
[One (M9) Android Development] LeeDroid:
Happy days!... thanks for your patience, we got there jn the end! :)

Have pushed R76 which limits the custom kernel installation to International and AT&T, you won't even see the option;)
[One (M9) Android Development] fernando sor:
Anyone else having the recents button mapped to menu fc? It force closes sense home. Meaning whether you have it set for press or long press.

Usually after the phone reboots or if I haven't used it in a while. Doesn't happen every time though.
[One (M9) Android Development] twinnfamous:
Not working for me either Lee
[One (M9) Android Development] wickedmx:
[MENTION=398245]LeeDroid[/MENTION] or anyone else who could possibly help. Any chance of getting a mirror link for the latest nightly from a platform with a bit more available bandwidth? The last few times I've tried downloading nightlies, I am getting speeds of between 6-20KB/s with current download completion estimates of about 2 days. It just seems to be an issue with the renovate-themes server as I am getting normal speeds of 1.2-1.5MB/s when testing to other locations across Europe.
[One (M9) Android Development] cobrax2:
yes s-off and twrp 2.8.7.1
[One (M9) Android Development] riyan ramadhan:
Gg
[One (M9) Android Development] cobrax2:
hmm now i cant copy my virtual sd to computer to backup:(

it copies about 3-400mb and then quits... like it's done!

the problem is that it doesnt "see" the other files, as if they dont exist!
[One (M9) Android Development] cobrax2:
ok, i wiped from twrp, now i dont have all apps lol.

upgraded to twrp 3.002. maybe now it will be better :)

---------- Post added at 11:17 AM ---------- Previous post was at 10:25 AM ----------

ok, now i have a clean install...

so i guess you need to erase all from twrp and then reinstall twrp 3+ to get all the apps?

or did i do something wrong?
[One (M9) Android Development] cobrax2:
looks like i solved my dnd notification problem though lol
[One (M9) Android Development] LeeDroid:
That's positive!... the actual wipe script it's self hasn't changed so not sure why your having a battle there, will test later, I would check your sdcard for errors if your having problems with it mate
[One (M9) Android Development] frank116:
Dear Lee

I have a question. When I install this rom, I can't find the Chinese language. Did you remove this language? Can you put the Chinese language back? Thanks a lot.
[One (M9) Android Development] LeeDroid:
Still working on my locales list mate, turned out it was causing a fee lags :confused: give morelocale a try for the moment, Chinese will be back soon
[One (M9) Android Development] deol 4ever:
Hey guys can anyone help me out? Flashed the rom it's running great but the emojis are ugly as hell , the lollipop version of this rom had the nice emojis does anyone know how I can get them back?
[One (M9) Android Development] LeeDroid:
Marshmallow imoji, they have grown on me lol, they ate usually built into framework and a bit of a pain to replace
[One (M9) Android Development] deol 4ever:
Oh okay that's alright not a problem I installed emoji switcher from the app store and it does the same thing, it doesn't have the htc emojis though. I was reading through the thread and I have tmous, I should be flashing the stock kernel right? I selected the leedroid kernel and the phone doesn't seem smooth it pays a bit. Thanks again for the rom!
[One (M9) Android Development] LeeDroid:
Check settings and see if it's installed mate, if it boots all will be well, my kernel should be smoother than stock, just takes a while for the ROM to settle.

Depending on the build you installed, the custom kernel option may have been blocked anyway
[One (M9) Android Development] migascalp:
have you seen this?

Work great on my m8 and m9
[One (M9) Android Development] 00bofh:
Any ideas what might have gone sideways on me?

One M9, TMoUS

On an "svn update", the latest revision (r76) failed during Aroma install with:

file_getprop: failed to stat
"/tmp/aroma-data/kernel.prop": No such file or directory

The logfile (attached) seems to agree with the message.

I wiped and re-downloaded the SVN and still ended up with a failed install.

I checked to make sure that

something

was referencing kernel.prop and found:

$ grep -ir 'kernel.prop' v8.0.0/*
v8.0.0/META-INF/com/google/android/aroma-config: "kernel.prop",
v8.0.0/META-INF/com/google/android/updater-script: file_getprop("/tmp/aroma-data/kernel.prop","selected.0") == "2"

and also made sure that aroma-config and updater-script made it into the ZIP file:

$ unzip -lv LeeDrOiD-OneM9-V8.0.0r76a.zip META-INF/com/google/android/aroma-config
Archive: LeeDrOiD-OneM9-V8.0.0r76a.zip
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
7646 Defl:X 2659 65% 02-27-2016 12:24 d6d19eaf META-INF/com/google/android/aroma-config
-------- ------- --- -------
7646 2659 65% 1 file

$ unzip -lv LeeDrOiD-OneM9-V8.0.0r76a.zip META-INF/com/google/android/updater-script
Archive: LeeDrOiD-OneM9-V8.0.0r76a.zip
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
64005 Defl:X 8008 88% 02-27-2016 12:24 7d546a2d META-INF/com/google/android/updater-script
-------- ------- --- -------
64005 8008 88% 1 file

Rolled back to r72, installed with no issues and it works fine.

Anything I can provide to further diagnoses? Brickbats because I missed something simple/stupid which will enable success?
[One (M9) Android Development] twinnfamous:
Install Failed for me too with r76
[One (M9) Android Development] kelvin216:
Failed

Can confirm T-Mobile option fails on R76 build
[One (M9) Android Development] LeeDroid:
Know what it is, the file isn't being created because you guys have selected tmo, likely the same for sprint, will fix it now