yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Golv:
Does anyone have a problem with the latest Magisk - c4377ed (SN not passed) from Rev.44?

Uninstalled c4377ed and installed 54e6a79 - SN passed

Uninstalled 54e6a79 and installed c4377ed - SN NOT passed.
[One (M9) Android Development] blueberry60:
I haven't got any problem with latest Magisk, SafetyNet Check was passed succesfully on Rev.44.
[One (M9) Android Development] Golv:
Removed Magisk with Magisk uninstaller in TWRP, cleared all Magisk references in /data, /data/app, /cache, flashed stock boot.img from rev.44 and reinstalled Magisk-c4377ed again.

Now everything is OK. SafetyNet Check was passed succesfully too.
[One (M9) Android Development] AYAN5525:
Nothing ???? No Working Totallity ?
[One (M9) Android Development] Golv:
Sorry. I don't use MultiUser, so I cann't say anything.

Have you checked this on stock rom?
[One (M9) Android Development] AYAN5525:
Yeah, Rom Stock Disable option MultiUser . LeedDrOiD enable its Option Mutiuser but no dowloading HOME .

Other Bug is No Running 8 cores, Stopped 4 cores no CPU 4 , CPU 5, CPU 6 , CPU 7.

is normal or no option for actived ???

Thanks for your answers :good:
[One (M9) Android Development] LeeDroid:
The 2nd 4 cores only come online when really needed, if they were all online you would be able to cook an egg on your M9 because the SOC is terrible
[One (M9) Android Development] AYAN5525:
hahaahha **** an egg hahaha :D :D :D :D

Thanks for resolved my Question.

Waiting answer only Multi User that i did,
[One (M9) Android Development] LeeDroid:
Haven't played much with multi user but I will get round to looking at it
[One (M9) Android Development] AYAN5525:
Thanks , Thanks for you support. Really interesed for the people and the bug a Rom LeeDroid, The best Rom based Sense. Waiting a refresh Rom .

Multi User my favorite option for the privacity my Girl Friend .... ;)
[One (M9) Android Development] calikevin:
Is anyone else able to access the AT&T NextGenPhone APN with their M9 and the MM ROM? For some reason I am unable to receive 4G speeds with my M9, but when I put my SIM into a Note 4 it gets LTE right away. Could this be a kernel or ROM issue?
[One (M9) Android Development] shpitz461:
I'm on NextGenPhone with the N rom and it's working great (even though I had much better speeds with TMO than now with AT&T, I guess AT&T towers are pretty congested).
[One (M9) Android Development] calikevin:
I should have mentioned I am on AT&T, seems to work fine on an AT&T branded Note 4 but not my unlocked international M9... pretty sure it worked a while back but not anymore, not for the last 6 months at least.
[One (M9) Android Development] shpitz461:
I figured you're on AT&T :)

Not sure what to tell you... I'm on the unlocked international as well, and it's working fine. Which firmware are you on? maybe that's the issue...
[One (M9) Android Development] bothered:
Downloaded svnzipper cant see option for m9, am i missing something?

SOLVED

EDIT: I was using v1 .0.6, the m9 is within the v1.0.5
[One (M9) Android Development] LeeDroid:
Grab it from here...

http://www.soldier9312-xda.de/svn/leedroid-m9/trunk/
[One (M9) Android Development] 00bofh:
Pulled the most recent SVN build via SvnZipper.exe (Port LeeDrOiD 10, v3.8.0 R92, Rev 44)

Installed selecting "T-Mobile US" as my carrier option (this is correct).

Installed - functions fine except for tethering.

Very slow /spotty connection when tethered, so I ran the NetFlix speedtest (problematic - trouble reaching servers and max speed of 4.3kBps) and noted multiple "hits" for:

07-06 07:28:55.546 D/TelephonyCallback(3906): DataActivity: 2
07-06 07:28:55.547 D/DATA_ICON(3906): dataConnected: true/true mMobileDataEnabled : true
07-06 07:28:55.548 D/StatusBar.NetworkController(3906): dumpIcon[stat_sys_data_out_tmous_lte stat_sys_5signal_4|null (gone) (gone) F]
07-06 07:28:55.728 E/McClient(1903): *****************************
07-06 07:28:55.728 E/McClient(1903): *** ERROR: connect() failed with "Connection refused"(errno 111)
07-06 07:28:55.728 E/McClient(1903): *** Detected in connect/109()
07-06 07:28:55.728 E/McClient(1903): *****************************
07-06 07:28:55.728 E/McDriverClient(1903): No route to host in open
07-06 07:28:55.729 E/TeeSyProxyServer(1903): *****************************
07-06 07:28:55.729 E/TeeSyProxyServer(1903): *** ERROR: open driver failed with "No route to host"(errno 113)
07-06 07:28:55.729 E/TeeSyProxyServer(1903): *** Detected in open/182()
07-06 07:28:55.729 E/TeeSyProxyServer(1903): *****************************
07-06 07:28:55.957 D/WFCService(4389): onSignalStrengthsChanged
07-06 07:28:55.958 D/TelephonyCallback(3906): SignalStrength: 4
07-06 07:28:55.958 D/SIGNAL_ICON(3906): level=4/5
07-06 07:28:55.958 D/StatusBar.NetworkController(3906): dumpIcon[stat_sys_data_out_tmous_lte stat_sys_5signal_4|null (gone) (gone) F]
07-06 07:28:56.038 D/WFCService(4389): updateWifiNotification, removed: false, task: true, cn:

in the logs (full capture attached).

Something is still a bit wonky for tethering. Checked the settings in /system/customize/ACC/default.xml and /system/build.prop as suggested in a prior answer by GOLV, other than hardcoding to TMOUS I didn't spot any issues. Setting the hard-code did not fix the problem.

Rolled back to ICE 557 R644 and had no issues.

Anything else I can do to help debug the weirdness?
[One (M9) Android Development] calikevin:
I'm on MM firmware, the Note 4 that works with the NextGenPhone APN is using 4.4.4

I really have no clue, and I've tried changing ROMs and everything.
[One (M9) Android Development] shpitz461:
Any reason why you're not on latest & greatest? check out the firmware thread. Try upgrading firmware and see if that solves your issue.
[One (M9) Android Development] ahmadmg:
Guys i'm having issues pulling the latest update using svnZipper,i think its because i'm having an unstable network.

Can anybody help me with the zip file plss???
[One (M9) Android Development] lingo2012:
Im on the latest nougat developer edition. When i flash the nougat rom it sits at the htc logo. I waited about 35 40 mins still nothing.
[One (M9) Android Development] calikevin:
Yes, no xposed or hide mock locations, so I'm not upgrading past Marshmallow.
[One (M9) Android Development] blueberry60:
SVN is almost updating revisions like LOS Nightly, Rev.45 is on...:) Thx to [MENTION=4445238]Golv[/MENTION] and [MENTION=398245]LeeDroid[/MENTION] for great effort.
[One (M9) Android Development] LeeDroid:
The base and mods are mine but [MENTION=4445238]Golv[/MENTION] is working like a trooper to get everything working on the M9 :laugh:
[One (M9) Android Development] Golv:
*HTC_M9-port_LeeDrOiD_10_V3.8.0-Stable-R92_rev.45

THX [MENTION=398245]LeeDroid[/MENTION]

*HTC_M9-port_LeeDrOiD_10_V3.8.0-Stable-R92_rev.45

- some TMoUS changes

- Add Tweak: Remove caller photo mask

- Fix Tweak: Big Caller Photo

- Update LeeDrOiD Tweaks & Shortcutter

- Fix Sprint HotSpot

- Update Shortcutter & in-built apps

- Update Magisk V13 BETA - c4377ed

- clean up

- updated InCallUI apk

- Fix SeLinux option

- some fix for TMoUS hotspot

- Bump to Stable V3.8.0 (HTC10)

- Updated HTC Mail & Exchange Hack - Thanks [MENTION=5530789]electronig[/MENTION] Punk

- Sprint - Test - Fix HFA

- App updates
​

Don't forget to make full nandroid backup before installing.

If you want V4A for this port rom version you can download it here - V4A_2.5.0.5_FULL_Install_LEEDROID.zip and Viper4Android 2.5.0.5 apk

SVN Nightly Zipper (v.1.0.5) for M9: http://www.soldier9312-xda.de/svn/leedroid-m9/trunk/svnZipper.exe

Download full rom: link
[One (M9) Android Development] daheufster:
For verification, SVN is using Nougat as a base with out M10 software. I am correct ?, where to find the M10 port in SVN?
[One (M9) Android Development] Golv:
Correctly. You can find all info here - https://xdaforums.com/showpost.php?p=72501413&postcount=8660
[One (M9) Android Development] LeeDroid:
Updates pushed to the HTC 10 buddy
[One (M9) Android Development] Golv:
SVN update

SVN for M9 is up to date too!

Rev.46

- Update Google Contacts & Dialer - Thanks [MENTION=506238]OMJ[/MENTION]!

- Update Shortcutter V2.6.3 Beta

- Update LeeDrOiD Tweaks V10.0.15

- Enable Tweak - Enable 4G/LTE Mixed Mode Icon​
[One (M9) Android Development] lingo2012:
Never mind running a different rom thanks anyway.
[One (M9) Android Development] 00bofh:
Port from LeeDrOiD 10 v3.8.0 R93 rev 46

TMoUS

So close...

WiFi tethering worked for about half an hour - then there was a Hotspot "crash" (silently stopped working).

Reboot post Hotspot crash restored Hotspot, but traffic now refuses to pass.

Log file attached, but the event looks very similar to rev 44:

07-07 14:24:08.078 D/TelephonyCallback(2918): DataActivity: 0
07-07 14:24:08.078 D/DATA_ICON(2918): dataConnected: true/true mMobileDataEnabled : true
07-07 14:24:08.080 D/StatusBar.NetworkController(2918): dumpIcon[stat_sys_data_connected_tmous_lte stat_sys_5signal_4|null (gone) (gone) F]
07-07 14:24:08.096 D/StatusBarManagerService(2212): setSystemUiVisibility(0x8008)
07-07 14:24:08.096 D/StatusBarManagerService(2212): disable:userId=0 what=0x0 which=0x1 pkg=null
07-07 14:24:08.096 D/StatusBarManagerService(2212): hiding MENU key
07-07 14:24:08.312 D/StatusBarManagerService(2212): setSystemUiVisibility(0x8008)
07-07 14:24:08.312 D/StatusBarManagerService(2212): disable:userId=0 what=0x0 which=0x1 pkg=null
07-07 14:24:08.313 D/StatusBarManagerService(2212): hiding MENU key
07-07 14:24:08.336 E/McClient(1740): *****************************
07-07 14:24:08.336 E/McClient(1740): *** ERROR: connect() failed with "Connection refused"(errno 111)
07-07 14:24:08.336 E/McClient(1740): *** Detected in connect/109()
07-07 14:24:08.336 E/McClient(1740): *****************************
07-07 14:24:08.336 E/McDriverClient(1740): No route to host in open
07-07 14:24:08.336 E/TeeSyProxyServer(1740): *****************************
07-07 14:24:08.336 E/TeeSyProxyServer(1740): *** ERROR: open driver failed with "No route to host"(errno 113)
07-07 14:24:08.336 E/TeeSyProxyServer(1740): *** Detected in open/182()
07-07 14:24:08.336 E/TeeSyProxyServer(1740): *****************************
07-07 14:24:08.382 D/WFCService(3364): updateWifiNotification, removed: false, task: true, cn: ComponentInfo{com.pluscubed.matlog/com.pluscubed.logcat.ui.LogcatActivity}, mWifiFit: DISCONNECTED, mNotificationEnabled: true
07-07 14:24:08.383 D/WifiManager(3364): getScanResults: Base Package Name=com.htc.wfcservice, uid=2903
07-07 14:24:08.384 D/WFCService(3364): updateWifiNotification scanResult: 0

If anyone can think of any other troubleshooting I can do or provide, please let me know.
[One (M9) Android Development] Golv:
Your part of log the same as from LeeDriod HTC 10 thread - https://xdaforums.com/showpost.php?p=72939045&postcount=19421
[One (M9) Android Development] LeeDroid:
Just pushed some bits buddy
[One (M9) Android Development] Golv:
SVN update

SVN is up to date.

Rev.48

* Re-Add & update Google Dialler & Contacts

* Update Shortcutter V2.6.6

- Tile colour corrections

- New features

- Bud fixes

* App updates

* System clean-ups​

Rev.47

* Remove Google Contacts & Dialler Option

- latest update is incompatible

* Update Shorcutter V2.6.4

- New Weather Tile

- Additional security against apk cracking

- Add humidity to weather view

- Fix tiles going to sleep & becoming unresponsive

* Remove redundant Goolgle Assistant Aroma option

* Fix init.d support!

- permissive Aroma option fixed​
[One (M9) Android Development] Golv:
SVN update

SVN is up to date again.

Rev.49

* Bump to Stable V3.8.1 (HTC10)

* Update Google Dialler

* Update Shortcutter​
[One (M9) Android Development] 00bofh:
OK - didn't know that, but my highlight now seems unrelated to the problem.

As I noted in my earlier post, what I spotted in the logs might be relevant, or it might be complete male bovine excrement.

What I do know is that from an experiential standpoint, "Mobile Hotspot" - a.k.a. "Tethering" is not yet reliable on the Port from LeeDrOiD 10 version, so I have been posting full logcat's hoping that someone smarter than me can figure it out.

I've seen a few others in here with similar issues, so if there's anything else needed to help debug what's going on - let me know so I can provide what little help an end-user is capable of...

Thanks!
[One (M9) Android Development] shpitz461:
I dirty-flashed r46 over r45 (i believe) and ever since I'm having terrible touch-screen response. I cleared dalvik after flashing rom and rebooted.

I need to press navbar many times for it to register a click, sometimes turning screen off and back on makes it a little more responsive, but even in apps the touchscreen is very unresponsive.

Anyone else?

EDIT: Looks like my touch-screen issue is gone, turned out my SD card (external) to be full, realized that when tried to copy r49.zip to it... :)
[One (M9) Android Development] Golv:
SVN Zipper for Windows v.1.0.7 and Guide on http://www.leedroid.co.uk :good:

SVN update:

Rev.51

- Latest Stable Magisk Version: v13.1

- Latest Magisk Manager Version: v5.0.4​
[One (M9) Android Development] Golv:
[MENTION=398245]LeeDroid[/MENTION]

Please can you look and try to fix a few problems?

1. Long press back key to kill app

2. Icons in one place on the main screen

3. App names in the application menu
[One (M9) Android Development] LeeDroid:
I can look at the first issue, but issues 2 & 3 are HTC problems I can't do much with, landscape isn't officially supported so it's a nightmare to try and resolve
[One (M9) Android Development] Golv:
SVN update

[MENTION=2563714]00bofh[/MENTION] Please check and let me know about results.

SVN is up to date.

Rev.53

- full updated TMoUS support based on 2.41.531.44 (HTC10)​
[One (M9) Android Development] shpitz461:
You are on fire!

a few minutes was getting r52, and now r53 is out already :)
[One (M9) Android Development] LeeDroid:
[MENTION=4445238]Golv[/MENTION] on a mission!
[One (M9) Android Development] Golv:
Yep!:D
[One (M9) Android Development] Skorpyun812:
Golv, wonderful job. Listen, I just refurbed this himawl with a new digitizer, frame, battery cover and upgraded 3000mah battery, charger case adds an additional 3200mAh and a new privacy screen protector. Looks like a new phone again. But then, same old Android M. Ok so LeeDrOiD IS THE BEST and MOST STABLE ROM I have ever run on this thing but, with all the shiny new parts, I wanted Android N. I dicked around with all these lineage OS variants after I Resurrected my vzw m9, to which I will not naim.... ? And they had headphone volume problems, Google Assistant problems, all kinds of ****e won't with them. I conceded. No N based ROM for this himawl. So back to Lee's R34 build, stored on my sd. Then I came back to this thread, downloaded your r92 build and everything works. No fukn issues at all! My phone looks like a brand new, slightly upgraded M9 and interfaces like a damn Galaxy s8! I even got my vvm back. I can rupture my ear drums in the car through my aux Jack thanks to you and Spotify. You have done a wonderful job at continuing where Lee left off.

I'll say it, LeeDrOiD IS THE BEST, PERIOD, END OF DISCUSSION! And it is thanks to the work you both have done.

Now to locate your donate button.
[One (M9) Android Development] Golv:
Thanks buddy!

Very appreciated. :o

I'm sorry but I cant send you tweaks key because I don't have it too.

But I can kindly ask [MENTION=398245]LeeDroid[/MENTION] send it to you. ;)

Thanks again!
[One (M9) Android Development] LeeDroid:
Tweaks key sent bud
[One (M9) Android Development] Skorpyun812:
Thank you both but I still have the one from when I donated to r33. It's very generous of you. I will keep it on another sd in case I ever erase the one I have. ?

---------- Post added at 03:51 PM ---------- Previous post was at 03:45 PM ----------

You should consider an LeeDrOiD/HTC logo with a crown. LeeDrOiD is King!

I don't just say this. I've tried so many other ROMs on this bastard, all of them have issues except LD. Your ROM is the only one that works completely, for the common user like myself.
[One (M9) Android Development] LeeDroid:
Always good to hear buddy! & [MENTION=4445238]Golv[/MENTION] has done a fantastic job of porting it :)
[One (M9) Android Development] 00bofh:
[MENTION=4445238]Golv[/MENTION]

New issue - SIM card is unrecognized by the ROM.

Two full clean installs, one dirty install on top of the second clean install.

Same issue each time.

Latest install/recovery logs attached. Unable to get MatLog (or other root log parser) to install, or ADB to respond, so nothing further (unless there's a hidden log file somewhere???).

Follow-up; restore to ICE restored phone service, so it's not the physical SIM card.
[One (M9) Android Development] blueberry60:
[MENTION=4445238]Golv[/MENTION] and [MENTION=398245]LeeDroid[/MENTION]

Do you think to update security with June Security Patch from HTC10 2.50.617.2 base?
[One (M9) Android Development] LeeDroid:
I am still waiting for HTC Europe to pull their fingers out of their bottoms and push us an update to the 10
[One (M9) Android Development] DAIDY:
This
[One (M9) Android Development] LeeDroid:
That's the beast
[One (M9) Android Development] Captain_Throwback:
But the kernel can handle arm or arm64, and that wouldn't really explain why the device is booting into bootloader after flash.

A last_kmsg from recovery after a failed flash might be helpful. adb pull /proc/last_kmsg for anyone facing this issue. Maybe then I can see why the ROM isn't loading. Everything recovery-side seems fine, though.

And SuperSU always throws a bunch of errors. Most of those are just because the zip tries to do things several different ways, and performs specific operations based on specific device types. Most of them don't apply to our device, so they show up as errors. I think SuperSU is probably the last thing you need to worry about in there.
[One (M9) Android Development] LeeDroid:
No kernel issues IMO, I was paying reference to Sqlite3 and zipalign binairies in the ROM, they throw a few issues as they were compiled for armv7 but nothing that would cause a failed boot.

It's got me a little stumped too...

Didn't think supersu was the issue, Just never paid attention to the supersu part of the log as it simply works...
[One (M9) Android Development] Captain_Throwback:
I'm asking for last_kmsg so I can see the bootloader logs from the boot up, since that appears to be where it's failing . . .
[One (M9) Android Development] LeeDroid:
I clearly got my wires crossed a little.. too many conversations going on ?

If anyone faces the failed boot issue can you please fulfill the above request?

Edit:

Just looked back and there was no mention of it booting to bootloader mate, it simply got stuck when booting...

Note to anyone reading the thread for the first time... This isn't a common issue, we are simply trying to establish why the issue occurred
[One (M9) Android Development] mikey_sk:
ok rom on and been messing about with it. much snappier than the stock so happy. its odd as i am so used to using completely different look and feel AOSP roms with devices such as the Nexus 6 and the Oppo Find 7- which are both a flashaholics circle jerk!

overall i prefer your rom over Venom as that seemed to make the icons look rather stretched so wiped it.

green battery won't win any icon design awards :) any way of turning it off under tweaks? :)
[One (M9) Android Development] LeeDroid:
No mate that ones an aroma option, if you flash the 7.3.0 > 7.3.1 patch over your install, the option is in there, so no messing around with a re-flash & optimizing apps etc ?
[One (M9) Android Development] DAIDY:
Thanks Lee .. waiting a few days to flash firmware when procedure is correct without reboot and heart attacks :crying:
[One (M9) Android Development] cables2590:
Lee I really enjoy this rom but the only issue I have is not being able to receive I coming calls... Im on at&t and someone has suggested to turn off volte but I cant find it. Do you have any other suggestions? I really want to use the rom...
[One (M9) Android Development] drmoeed:
"Just to clarify" :-

Exactly ... It stucked after bootsplash on a blank screen ... No boot ...

what I noticed was that device was heating up as it does on normal first boot of any rom and optimizing app ... But the screen never showed up ...

In 7.3.1, I rebooted into recovery from that blank screen and dirty flashed the ROM again and it did get boot up that tym ...
[One (M9) Android Development] LeeDroid:
Hi mate, I'm not really versed in the ways of AT&T so it's a difficult supporting piece, did you try flashing and selecting international instead?
[One (M9) Android Development] cables2590:
Thanks for the response, but where do I choose international at? At first boot up or on the aroma flash screen?
[One (M9) Android Development] LeeDroid:
In the aroma installer matey
[One (M9) Android Development] cables2590:
I'm going to try that again but I dont remember seeing that option...
[One (M9) Android Development] LeeDroid:
Carrier selection is right at the start of the installer, international is default
[One (M9) Android Development] Captain_Throwback:
Doesn't change what I need, but thanks for the clarification. It's still not booting, whether it's to bootloader or just stuck at boot splash. Just trying to help figure this out.
[One (M9) Android Development] LeeDroid:
It's appreciated mate, no more reports and nothing standing out, hopefully it was just a freaky 1 off since the updater fixes went in
[One (M9) Android Development] cables2590:
Thanks for trying but that didn't work either... I did not have Internet service... When asking for carrier I just pressed next but that didn't seem to work... Im just going to have to go back stock for now...
[One (M9) Android Development] LeeDroid:
I will have to investigate mate, having to remove carrier support for the moment (mentioned a few pages back), it will return and I'm sure all of the creases will be ironed out
[One (M9) Android Development] Golv:
If you send me 2 folders from HTC10 2.50.617.2 base then I will update the Security System.

I need /system/lib and /system/lib64 folders.

---------- Post added at 11:50 ---------- Previous post was at 11:31 ----------

SVN update

Rev.54

- hope fixed NO SIM card issue for TMoUS (THX [MENTION=2563714]00bofh[/MENTION] )​

Please check!
[One (M9) Android Development] blueberry60:
[MENTION=4445238]Golv[/MENTION] here are lib folders for June Security Patch:

2.50.617.2_lib folders.zip
[One (M9) Android Development] Golv:
SVN update

SVN update:

Rev.56

- updated Stagefright Security patch 2017-6-1 THX [MENTION=3182548]blueberry60[/MENTION]​
[One (M9) Android Development] blueberry60:
Thx our M9 trooper for quick SVN Update..:)
[One (M9) Android Development] Golv:
SVN update

Rev.57

- Update Google Dialler & Contacts (With support jar - Thanks [MENTION=2401586]jsaxon2[/MENTION])

- Update Shortcutter & In-built applications

- Increase SMS sizes for Verizon users

- some customize changes​
[One (M9) Android Development] 00bofh:
SIM recognition is fixed!

Looks like tethering on TMoUS is going to be the bugbear though...

Still no luck, though the behavior has changed slightly.

On initial request to "fast dot com", zero bytes are transferred for 45 seconds or so, then a "burst" to almost 1.5 Mbps, then some variable smaller bursts from 4 to 750 Kbps.

Eventually the test fails with "unable to reach the server".

By comparison, ICE 5.5.7 runs steady at 11-14 Mbps across several tests.

The usual log files attached, syslog from about two seconds before I started the fast dot com test until it failed.

Nothing stands out except for "Not a typewriter" messages every now and again (has someone been binge watching Red Dwarf??? ;) )
[One (M9) Android Development] guidogsbn:
Magisk 13.2 is out, can be updated by magisk app:cool:
[One (M9) Android Development] Golv:
SVN update

Rev.59

- Latest Stable Magisk Version: v13.2

- Latest Magisk Manager Version: v5.0.5

- changes for TMoUS​