yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] trjlive:
[MENTION=1186202]baadnewz[/MENTION] doesn't like mirrors, the ad income he makes from his site help support the rom.

I've found if the download is going super slow, just cancel it, close the page, clear your cache, and then re-try. Always seems to give me a faster download - probably hitting a faster server. :)
[One (M7) Android Development] zounduser:
Good to know. Thanks my dude.
[One (M7) Android Development] lazyluis32:
What kernel are you guys using?
[One (M7) Android Development] vinistois:
I am on a Bell variant.

LTE reception is awful, usually just one bar. When I was using ARHD, there was a setting for Bell users to correct the reception issue. Is there something similar available or some other hack?
[One (M7) Android Development] trjlive:
The one-bar LTE is actually pretty normal. The issue actually stems from the way LTE signal is measured versus HSPA signal. The roms that "fix" the signal don't actually do anything to improve the reception. All they're doing is changing the scale that the rom shows the certain number of bars. So the "fixed" roms show more bars for the same signal.

If you really want to see the actual signal you have, use Network Signal Info (link) and look at the dBm reading on the "fixed" rom versus the non-fixed rom. They'll most likely be the same dBm reading, even if different bars are showing.

The best way to improve reception is try various radios until you find the one that actually gives you the best signal. Using the app I linked above, flash different radios and monitor the reception in different areas. When you find the best one, stick with it. Previously, I'd been using the GPE radio 4A.18.3263.15 which gave me the best reception, even better than the new radios. Today I updated to the brand new T-Mobile US radio 4A.20.3263.30 and it's better than the GPE, at least in the area I'm in.

So it's really just a matter of trial and error to find the radio that works the best for you. But no rom can significantly improve your reception or signal, all they can do is make it seem like you have a better signal by inflating the number of bars you see.

Hope that helps clear it up. :)

Check out this thread for the different radios (link). You can just flash the zip file in recovery like any other zip, doesn't clear any data, just flash, reboot, and test! Don't like it, download another one, flash, reboot, test again!
[One (M7) Android Development] chrisrj28:
From what I understood editing that only works on a fresh install and doesn't allow changing on the fly
[One (M7) Android Development] vinistois:
Thanks very much for your very detailed reply - really appreciated.

I guess then the number of bars is not a problem. But the bad reception definitely is. I frequently get errors in gmail and youtube that I don't have a connection. This happens when I am trying to refresh the inbox or play a video. I just hit retry 5-15 times and then it will work. Very annoying. Its weird because with youtube, it will be playing a video just fine, then if I try to play the next one it will say no connection. But hit retry a bunch and then it plays fine. So it seems that while it has a connection, it is a good one, but it has difficulty "initiating" a new connection.

Naturally I attributed all this to the display showing only 1 bar most of the time. But I guess its more complicated than that!

Can anyone recommend a good radio for Bell in the Vancouver area? There is nothing for Bell in the radio threads.
[One (M7) Android Development] b00f13:
Just noting that selecting "70% Transparent Notification Bar" auto-selects 70% Transparent Notification Drop-Down. If there was any way of separating the two that'd be great!
[One (M7) Android Development] formula84:
Would it be better to get the file from the 4.3 base update from today?

I wonder if this has anything to do with the mix of people reporting camera issues with pano360... One user with superCID + latest firmware and same rom... And another with exact same setup had it working only difference was their models. The t-mobile user was the one having issues.
[One (M7) Android Development] trjlive:
If you change the xml file and then run the following command, it will take effect. Granted, it does reset your Sense settings and home screen layouts back to default first-run.

$ adb shell am start -n com.htc.android.htcsetupwizard/.activity.CustomizationActivity

I originally learned this method from this post: link

So if your method doesn't reset Sense settings, looks like it's the better method. I was using my method as part of my build script before zipping up the svn source before Baad added the MMS mod to the rom. Since then, however, I haven't needed to make the edits.

---------- Post added at 09:45 PM ---------- Previous post was at 09:39 PM ----------

I would recommend you try the GPE 4.3 radio first (4A.18.3263.15 - link). That is the one Baad uses and I used for a long time with the best results, and many use it with great results. From there, depending on results, maybe try the Dev Edition 4.3 radio (4A.20.3263.16). I would stay away from the 4T radios, they tended to be the buggiest for people. The Dev Edition and GPE radios have generally been the best, but there are also areas where the T-Mobile or AT&T radio will work the best. Since Bell is GSM, I would make sure to only flash GSM radios, don't try anything that is for Verizon or Sprint, as they use different radio hardware. But as long as you're flashing GSM radios, worst that will happen is it just won't work, no reception. So reboot and flash a different one. I went through them all before I settled on the GPE version. It gave me the best reception in Portland, Seattle, San Francisco, Los Angeles, and Phoenix, which are the places I travel the most.

Update: [MENTION=3213097]vinistois[/MENTION] Another thought, did you choose the option in aroma to disable fast dormancy? Unless you know for sure your carrier is NOT using fast dormancy, disabling it can cause connection issues. The towers are expecting the device to behave with FD, but then your device is behaving without FD, so there is extra signaling and possible data drops. Leaving it with the default "undefined" setting lets the phone determine what the carrier's network is using.

---------- Post added at 09:50 PM ---------- Previous post was at 09:45 PM ----------

I wasn't sure what [MENTION=4457281]hawknest[/MENTION] was looking for in the ext.jar, he needed one from a stock tmous base, and that was the only one I had so that's why I attached it. You're probably right though, the new one from the 4.3 base would probably be better. If hawk wants the new one I can definitely pull and send it too.
[One (M7) Android Development] liney_2000:
You could use "speedtest" or similar app to get some signal data first, then try some different radios.

Have a look here for some more info and different radios.

I am using latest wwe radio and LTE speeds are great, and WIFI improved from last version, but whatever works for you - I am in a different hemisphere to you!!
[One (M7) Android Development] baadnewz:
t-mobile wifi calling

i know in the US is mostly Monday night but if anyone if bored or working the graveyard shift

r186

t-mobile wifi calling and several wifi improvements. needs testing. thanks
[One (M7) Android Development] baadnewz:
Sprint BT fix

also

r187

attempt to fix Sprint BT issues
[One (M7) Android Development] vinistois:
I think I may have discovered a new 5.5 feature.

I have the official car dock and was always disappointed that there was no landscape mode for the homescreen. I sometimes use car mode, but not always, so it was a pain to be stuck with a sideways homescreen.

Well, since the 5.5 update, the homescreen works in landscape mode! But, only when inserted in the dock.

Is this a feature of this rom, or of sense 5.5? I ask only because it is slightly broken with the 5x4 icon layout option. The icons look ok, but the widgets from the 3rd row are overlapping the second row icons.
[One (M7) Android Development] baadnewz:
is a feature of the base not the rom, and yes it might conflict with 4x5 mod.
[One (M7) Android Development] trjlive:
Ok I'm updating svn right now and will test the wifi calling. I've been looking forward to this day since I first unlocked and loaded a custom rom! :D
[One (M7) Android Development] yxtl:
Can you please post here Automotive_Home.apk?
[One (M7) Android Development] vinistois:
attached.
[One (M7) Android Development] yxtl:
thx alot man
[One (M7) Android Development] hawknest:
I got it thanks

Sent From My Dark EclipticONE
[One (M7) Android Development] SmiLey497:
T-Mobile IMS needs to be set to true in the default.xml however there is a FC with with phone after being set to true. Also trying to access the Wi-Fi calling settings causes a settings force closure.
[One (M7) Android Development] blu9987:
Just tested and I don't have wifi calling in my settings. I may just be blind though...
[One (M7) Android Development] pmacevad:
Anything worth upgrading for Sprint? Currently r181...

Edit. Duh, n/m. I guess I mean in r186

Sent from my rooted & s-off'd HTC One, powered by Android Jelly Bean v4.3 :)
[One (M7) Android Development] tnh196:
dont know if i missed it but i keep getting this message whenever i try to make a call, unfortunately, the process com.android.phone has stopped, any one know about this???
[One (M7) Android Development] baadnewz:
all right so wifi calling still no go :). will poke more
[One (M7) Android Development] trjlive:
version? carrier?
[One (M7) Android Development] Elim:
I can confirm this: BlinkFeed, the home screen layout and the widgets now work also perfect in landscape but the app-drawer for me still not... But it is time now for a tweak ?
[One (M7) Android Development] baadnewz:
r188 another attempt at tmo stuff
[One (M7) Android Development] trjlive:
just now did 187 and yeah it wasn't working. updating to r188 now. between the dog and the girlfriend and svn, my attention is getting pulled left and right :P
[One (M7) Android Development] scifitrekkie:
not on tmo, but giving 188 a bash now, thanks
[One (M7) Android Development] SmiLey497:
com.android.phone had stopped on r188
[One (M7) Android Development] baadnewz:
can you post a logcat for that error alone? might be missing a lib or some smali. i'm sure i can fix it once i have log
[One (M7) Android Development] trjlive:
com.android.phone has stopped on first boot up, appears over white htc screen, doesn't even get to the first run setup routine.

r188
[One (M7) Android Development] baadnewz:
logcat for that FC please.
[One (M7) Android Development] RuckusDecay:
Click on my signature for how to logcat. Get the exact problem.
[One (M7) Android Development] SmiLey497:
Alright, gotta re-enable IMS in default.xml again
[One (M7) Android Development] baadnewz:
tmo phone fc fix

to avoid you ziping all rom for a svn commit

flash this from recovery . let me know if it fixes TMO FC
[One (M7) Android Development] scifitrekkie:
OK for international :D
[One (M7) Android Development] trjlive:
Logcat attached. I did verbose since I didn't know what exactly you'd want to see. Let me know if you want it some other way.

I see a bunch of these errors:

[ 10-22 06:44:23.706 619: 2232 W/PackageManager ]
Unknown permission com.htc.lucy.permission.BACKUP_STATUS_UPDATE in package com.nero.android.htc.sync
[One (M7) Android Development] trjlive:
flashing it now, results to follow...
[One (M7) Android Development] baadnewz:
actually this is the error that is relevant for our research

[ 10-22 06:44:27.040 2405: 2405 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NullPointerException
at android.app.ActivityThread.handleBindApplication(ActivityThread.java)
at android.app.ActivityThread.access$1300(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.android.phone.PhoneInterfaceManager.<init>(PhoneInterfaceManager.java)
at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java)
at com.android.phone.PhoneApp.onCreate(PhoneApp.java)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java)
... 11 more
[One (M7) Android Development] SmiLey497:
No fix
[One (M7) Android Development] trjlive:
Flashed the tmo patch, cleared cache & dalvik, reboot got the same error.

New logcat attached.
[One (M7) Android Development] trjlive:
I know it's late for me on the west coast, but man it's 3am for you! And you're still flashing and testing and not totally f-ing up your phone! :D
[One (M7) Android Development] baadnewz:
do me one last favor, adb push the files in the zip

maybe something is wrong with the damn zip, just to eliminate everything
[One (M7) Android Development] SmiLey497:
I have a flight at 6:40am, so i'll catch up then, LOL.

---------- Post added at 03:02 AM ---------- Previous post was at 03:01 AM ----------

Pushed in recovery still same error.
[One (M7) Android Development] trjlive:
I had same as SmiLey497, pushed the individual files and still same error. :(
[One (M7) Android Development] baadnewz:
let me test something real quick .
[One (M7) Android Development] trjlive:
Ahh good plan! I have until my girlfriend gets tired of playing whatever game she's playing on our tablet and decides it's bed time, LOL.

---------- Post added at 12:09 AM ---------- Previous post was at 12:09 AM ----------

standing by, good sir!
[One (M7) Android Development] nur.salikeen:
Hi [MENTION=1186202]baadnewz[/MENTION],

I tried this command

adb shell
mke2fs /dev/block/mmcblk0p36

And I got this error:

Then I try this one

adb shell
mke2fs /dev/block/mmcblk0p35

and my rom got wiped. Try to clean flash 5.0-3 still stuck at HTC One boot.

Since 5.0-4 already available, I'm gonna try to clean flash latest version.

Anyone got solution for that error?
[One (M7) Android Development] baadnewz:
[MENTION=5362940]trjlive[/MENTION] [MENTION=1756722]SmiLey497[/MENTION]

can you push the attached Phone.apk to /system/app/

then adb reboot and see if its working.? thanks and sorry for using you for testing
[One (M7) Android Development] baadnewz:
why would you format p35 which is system ?

for the error you get while trying to format p36, type umount /cache before running the command.
[One (M7) Android Development] SmiLey497:
Still FC
[One (M7) Android Development] trjlive:
No need to apologize, it's my honor to be involved with the development process.

I pushed the file, rebooted, but got the same error.

I'm clearing caches now and rebooting again to see if it makes a difference.

Update: cleared caches and rebooted, no difference. still fc on com.android.phone.

Do you want another logcat after replacing the file?
[One (M7) Android Development] nur.salikeen:
Okay it work. Haha.

That wasn't your fault. It just my try and error behaviour. :silly:
[One (M7) Android Development] baadnewz:
yap give me a logcat, maybe something changed.
[One (M7) Android Development] SmiLey497:
Hope this helps. What about the Framework2.jar? I remember that was flashed as well on 4.1.2.

W/System.err(8031): java.lang.ClassNotFoundException: com.movial.ipphone.IPPhoneProxy
W/System.err(8031):	at java.lang.Class.classForName(Native Method)
W/System.err(8031):	at java.lang.Class.forName(Class.java)
W/System.err(8031):	at java.lang.Class.forName(Class.java)
W/System.err(8031):	at com.android.internal.telephony.PhoneController.createPhoneInstance(PhoneController.java)
W/System.err(8031):	at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java)
W/System.err(8031):	at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java)
W/System.err(8031):	at com.htc.wrap.com.android.internal.telephony.HtcWrapPhoneFactory.makeDefaultPhones(HtcWrapPhoneFactory.java)
W/System.err(8031):	at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:1955)
W/System.err(8031):	at com.android.phone.PhoneApp.onCreate(PhoneApp.java:38)
W/System.err(8031):	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java)
W/System.err(8031):	at android.app.ActivityThread.handleBindApplication(ActivityThread.java)
W/System.err(8031):	at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
W/System.err(8031):	at de.robv.android.xposed.XposedBridge.invokeOriginalMethod(XposedBridge.java:651)
W/System.err(8031):	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:482)
W/System.err(8031):	at android.app.ActivityThread.handleBindApplication(Native Method)
W/System.err(8031):	at android.app.ActivityThread.access$1300(ActivityThread.java)
W/System.err(8031):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
W/System.err(8031):	at android.os.Handler.dispatchMessage(Handler.java)
W/System.err(8031):	at android.os.Looper.loop(Looper.java)
W/System.err(8031):	at android.app.ActivityThread.main(ActivityThread.java)
W/System.err(8031):	at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(8031):	at java.lang.reflect.Method.invoke(Method.java)
W/System.err(8031):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
W/System.err(8031):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
W/System.err(8031):	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:115)
W/System.err(8031):	at dalvik.system.NativeStart.main(Native Method)
W/System.err(8031): Caused by: java.lang.NoClassDefFoundError: com/movial/ipphone/IPPhoneProxy
W/System.err(8031):	... 26 more
W/System.err(8031): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.movial.ipphone.IPPhoneProxy" on path: DexPathList[[zip file "/data/data/de.robv.android.xposed.installer/bin/XposedBridge.jar"],nativeLibraryDirectories=[/system/lib]]
W/System.err(8031):	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java)
W/System.err(8031):	at java.lang.ClassLoader.loadClass(ClassLoader.java)
W/System.err(8031):	at java.lang.ClassLoader.loadClass(ClassLoader.java)
W/System.err(8031):	... 26 more
W/dalvikvm(8031): threadid=1: thread exiting with uncaught exception (group=0x41617718)
[One (M7) Android Development] trjlive:
Here ya go. Full logcat attached, the phone error is below:

[ 10-22 07:37:18.141 7350: 7350 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NullPointerException
at android.app.ActivityThread.handleBindApplication(ActivityThread.java)
at android.app.ActivityThread.access$1300(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.android.phone.PhoneInterfaceManager.<init>(PhoneInterfaceManager.java)
at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java)
at com.android.phone.PhoneApp.onCreate(PhoneApp.java)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java)
... 11 more

[ 10-22 07:37:18.141 713: 2838 W/ActivityManager ]
Process com.android.phone has crashed too many times: killing!
[One (M7) Android Development] trjlive:
Hey when you pull your logcat, what flags are you using to limit it? I've been doing

-v long

to get verbose long format, but yours looks much more concise without so much cruft.
[One (M7) Android Development] baadnewz:
ok got it, need some time to figure it out, i tried all the easy to do fixes and nothing works, i have logcat and all i need, i just need the brains no.

to stop the Fc

edit /system/customize/ACC/default.xml

<app name="TMOUS_IMS">

<item type="boolean" name="enable_wifi_ims">true</item>

</app>

turn is to false will see more what i need to be doing to get it working
[One (M7) Android Development] RuckusDecay:
I installed the what I noticed is it says it was modified 2019 you think that's what it has to do it with. I got a fc once but is working now.
[One (M7) Android Development] SmiLey497:
I use Advanced Logcat Viewer
[One (M7) Android Development] SmiLey497:
What?????? What's working? I don't see the Wi-fi calling signal in the status bar. You're using regular signal.
[One (M7) Android Development] baadnewz:
here it is framework2.jar but i from what is in logcat is not related.

push it with the phone in recovery, wipe cache and dalvik before booting (use the latest phone.apk i provided )
[One (M7) Android Development] RuckusDecay:
The phone app right
[One (M7) Android Development] baadnewz:
i have an idea to work on, but it will take 30-40 mins, hopefully someone is still online to test
[One (M7) Android Development] SmiLey497:
Trying to get Wi-Fi calling to work, my man.
[One (M7) Android Development] RuckusDecay:
No when I was in es file explorer the date for the apk is 2019 not the 2013 which is weird right. So what I did was update the system with aroma then the dates change.
[One (M7) Android Development] SmiLey497:
Hopefully I haven't left for the airport by then.
[One (M7) Android Development] RuckusDecay:
You saw the pic I posted a couple post above so idk if it is or not but I was able to surf web while on the phone that s how it's supposed to work right.
[One (M7) Android Development] SmiLey497:
Framwork2.jar makes it worse with a Systemui FC.
[One (M7) Android Development] RuckusDecay:
Hey [MENTION=222268]smiley[/MENTION] can you check the date of the app that you downloaded the one baad posted.
[One (M7) Android Development] trjlive:
re-pushed the phone.apk you provided, pushed the framework2.jar, rebooted into recovery and cleared cache & dalvik, reboot system and still FC on phone error

There is a difference though, before pushing the framework, the system would get to the white HTC screen just before the first run setup and then the FC would appear. After pushing framework, it doesn't even get to the white htc before the FC appears. The FC pops up as soon the the boot logo with beats disappears, then screen goes black and FC pops up over black screen. So the framework certainly made some difference, just not what we're trying for, unfortunately.

---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------

That's not what we're working on, we're working on the T-Mobile wifi calling feature.
[One (M7) Android Development] S_Dot:
Can someone please tell me how to sign up for SVN? A link would be nice. Thank you.
[One (M7) Android Development] RuckusDecay:
Yeah I know but I'm not getting the fc anymore on the phone.apk
[One (M7) Android Development] trjlive:
https://insertcoin-m7-nightly.googlecode.com/svn/trunk/

That's the svn source url.

You can refer to one of my previous posts for some ideas on scripts to automate the sync and build process. (link)

---------- Post added at 01:04 AM ---------- Previous post was at 01:02 AM ----------

Are you on T-Mobile and running svn r188 and using the phone.apk and framework2.jar files baad provided?

The wifi calling is where the phone call goes over wifi instead of using cell service. It's a t-mobile feature. That's what we're working on implementing.
[One (M7) Android Development] RuckusDecay:
Yup