Chase Mobile banking app has been an on and off issue for a long while - various issues with my S2, S3, S4, Note2, and now my M8.
Up until they did an upgrade the app would only work on Sense based ROMs (some other theories out in the search realm where that the app checks for root or unlocked bootloader -- that is NOT the issue). All AOSP based ROMs or GPE ROMs would , when trying to do a mobile Deposit taking a image of the check within the app, return a solid green image. Currently with the latest update of the app the image is taken but the image in CM12, BlissPop, and / or GPE Roms is blurry ---- but using a Sense based ROM returns a useful image.
Is there any setting within the code for how an AOSP / GPE ROM uses the device camera that would cause the image to not focus properly? Contacting Chase app development is SLOW at best --- it took them over a year to solve the green image issue.
jcrompton said:
Chase Mobile banking app has been an on and off issue for a long while - various issues with my S2, S3, S4, Note2, and now my M8.
Up until they did an upgrade the app would only work on Sense based ROMs (some other theories out in the search realm where that the app checks for root or unlocked bootloader -- that is NOT the issue). All AOSP based ROMs or GPE ROMs would , when trying to do a mobile Deposit taking a image of the check within the app, return a solid green image. Currently with the latest update of the app the image is taken but the image in CM12, BlissPop, and / or GPE Roms is blurry ---- but using a Sense based ROM returns a useful image.
Is there any setting within the code for how an AOSP / GPE ROM uses the device camera that would cause the image to not focus properly? Contacting Chase app development is SLOW at best --- it took them over a year to solve the green image issue.
Click to expand...
Click to collapse
I'm having the same issue with blurry check deposit images using my bank's mobile app as well (Regions). I don't think it's necessarily due to not being on a sense-based rom, though, because I'm on InsertCoin 5.0.7 (sense).
When I'm on this stock ROM (pretty old, but the latest official offering from AT&T - http://www.htc.com/us/support/htc-one-m8-att/news/), I can use the mobile deposit feature, but when I'm on any of the newest Roms, like InsertCoin or this one(http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365), mobile deposit images are blurry.
I thought this might have to do with the updates that HTC made to the camera (where you can blur the background when taking pictures), but I haven't tested that theory. So, I think the banking app isn't using the updated camera app properly.
Any update or new discoveries? Or must one keep a nand backup of a sense ROM just to get the Chase app to function properly?
Still wondering.
Related
I have been browsing the forums for quite some time now and I have tried alot of roms. Every rom I have tried, has failed or is no longer supported. Can anyone reading this post please share a link or any other information regarding this help. I have the 5110 version note I appreciate all the help I can get.
Sent from my GT-N5110 using XDA Free mobile app
Anyone
Sent from my GT-N5110 using XDA-Developers mobile app
I forced myself to break away and lightly customize a stock ROM made for a provider. It is the only stock ROM that has stagefright fix which is way cool, and a few other usabililty fixes as well. Must allow security update to patch, it helps correct a few wee bugs.
The big issue... you are forced to keep a new boot loader, and cannot revert to any previous Stock ROM, and must deal with boot loader compatibilities unknown by builders as they have stopped with any new builds .
Downside, the new bootloader effects various Root functions. But newer Super Su, Boeffla utility, and other updated older Xposed modules seem to help with the new boot loader. Plus Default Apps no longer lists, but they can be managed through App Manager.
A custom SecSettings from a Note 2 (S5 varient) will bring back the Default Apps function plus many hidden settings options built in thus latest OEM build.
So, if you want all the bells and whistles, you will have to deal with the bugs, no matter how big or how small.
Now to explain what features I had with Gnabo v8 SE that I don't miss at all.
Mag UX, Tab Keyboard, Spen Air Command, 160dpi, Multi boot menu, and enhanced wallpaper picker.
Features I have and use, and are bug free but need a system UI to use them... tested with a custom Note 2 Secsettings that has some issues because it is a S5 variant and made for Note 2 specifically.
Colorblind, Interaction Control, Face Lock (came with my OEM build), Grey Scale (built in partially with new build, but S3 neo System UI is the key), Apps from a broken and defunct custom ROM for the N5110, Quick Connect 1.6.5.
My issues are minimal, but seem to be plagued by the new boot loader more than the ported apps.
Miracast works best, 3 minutes after reboot. WiFi is not stable after using hooked VPN apps of any type. Disabling WiFi for a minute and re enabling corrects the issue 80% of the time. A reboot may need to be done if WiFi is buggy. Reboots are 75% trouble free. Sometimes you get a fast boot soon after system UI loads, sometimes you get GMS forced closes, and must reboot.
It may be because of Triangle Away not being upgraded to work with newer boot loaders, or SU still needs some tweaks to work around the latest build by Samsung.
If I were stubborn I would stick with Gnabo v8 SE and it's patches and run Boeffla kernel, and just deal with 160dpi. But I am comfy with what I did even though the 75% boot issues and Miracast functionality being effected by WiFi with VPN apps.
I have given options for assistance by ROM builders in copying my ROM for building a unique custom one, but because I am using some apps that may be from a closed off ROM to builders, respect to the owners must be made. So it will be all for personal use at most.
Thanks for the detailed reply. I guess stock with some tweaks here and there isn't that bad afterall
Sent from my SM-G935F using XDA-Developers mobile app
as of late beoffla kernal utility works smoothly with its latest update.
Also I noticed better boot ups, so most of my boot issues are from beoffola utility with the new boot loader.
Plus, I had to manually remove earth, as google's earth app is busted for 218 220 dpi on the new rom. Google pushes that version from play store without installing the busted version. I downloaded he nodpi version and run it, just unable to update it through play store.
Also wifi seems to operate smoother changing from miracast, and vpn apps. again beoffola utility finally has gotten it right, to use on newer boot loaders, and the lastest OEM ROM.
Hi all.
I've got an taiwanese HTC 10 which is on the MM firmware, but I wish to try the Nougat on a custom ROM.
I realise that there is plenty of ROMs, but it seems that's nobody intention to stay close to the stock experience.
Is there any "untouched" Nougat ROM available to flash for S-On devices running MM firmware?
By "untouched" I mean the minimum necessary changes to make things compatible.
Thank in advance.
btoledob said:
Hi all.
I've got an taiwanese HTC 10 which is on the MM firmware, but I wish to try the Nougat on a custom ROM.
I realise that there is plenty of ROMs, but it seems that's nobody intention to stay close to the stock experience.
Is there any "untouched" Nougat ROM available to flash for S-On devices running MM firmware?
By "untouched" I mean the minimum necessary changes to make things compatible.
Thank in advance.
Click to expand...
Click to collapse
...our rom looks and feels complete stock if you install it, we also use the stock htc kernel.
All modifications are optional and can be configured in our Tweaks control app or flashed over our hub.
If you still care about that then flash MaximusHD, that's really the closest to stock..still has some modifications like extenced APM and maybe some other.
Still not safisfied? Then flash the stock deodexed Dev Edition Rom. Fingerprint will be broken, flash this to fix it: https://www.androidfilehost.com/?fid=529152257862688644
not sure what you mean with "minimum necessary changes to make things compatible" doubt any sense roms around here break stock features.
j to the 4n said:
...our rom looks and feels complete stock if you install it, we also use the stock htc kernel.
All modifications are optional and can be configured in our Tweaks control app or flashed over our hub.
If you still care about that then flash MaximusHD, that's really the closest to stock..still has some modifications like extenced APM and maybe some other.
Still not safisfied? Then flash the stock deodexed Dev Edition Rom. Fingerprint will be broken, flash this to fix it: https://www.androidfilehost.com/?fid=529152257862688644
not sure what you mean with "minimum necessary changes to make things compatible" doubt any sense roms around here break stock features.
Click to expand...
Click to collapse
Thank you very much for the feedback.
I've tried your ROM, which is excelent, but I got a little problem with the camera app. If I take a picture on the Pro mode with RAW enabled, the RAW image does not follow the device orientation, and consequently the Google Photo app does not suggest enhances, because the RAW and the JPEG are different from each other. I need to take pictures only on landscape mode and only with the home button on the right side in order to work properly. As I never had the opportunity to test the completly stock Nougat ROM from HTC, I don't know if this problem is specific to your ROM or from the HTC's Nougat source code.
The other ROM that I've tried is LeeDroid. I found a bug on his ROM where the default audio profile does not turn ON when playing some music on my headphones, so everytime I need reenable my profile in order to make it to work again. The other minor thing is that he changed the wallpapers.
As I never had the opportunity to test the completely stock Nougat ROM from HTC, I can't be sure if those glitches are avoidable.
btoledob said:
Thank you very much for the feedback.
I've tried your ROM, which is excelent, but I got a little problem with the camera app. If I take a picture on the Pro mode with RAW enabled, the RAW image does not follow the device orientation, and consequently the Google Photo app does not suggest enhances, because the RAW and the JPEG are different from each other. I need to take pictures only on landscape mode and only with the home button on the right side in order to work properly. As I never had the opportunity to test the completly stock Nougat ROM from HTC, I don't know if this problem is specific to your ROM or from the HTC's Nougat source code.
The other ROM that I've tried is LeeDroid. I found a bug on his ROM where the default audio profile does not turn ON when playing some music on my headphones, so everytime I need reenable my profile in order to make it to work again. The other minor thing is that he changed the wallpapers.
As I never had the opportunity to test the completely stock Nougat ROM from HTC, I can't be sure if those glitches are avoidable.
Click to expand...
Click to collapse
the roms are based on an unreleased WWE 2.28 leak...the offical WWE version will be 2.4x. Since it's a leak there seem to be a few bugs still. Should be sorted on the official one.
If you can't wait, you could s-off, change to dev ed cid and mid and flash the US Unlocked RUU.
For the issues with raw images...disable the google photo app and install the A9 Sense 8 Gallery and photoenhancer available in venomhub and check if it solves the issues.
Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.
Just need to have an unlocked M9
S-off is for downgrade firmware, change CID/MID... (more risk to brick )
dirtyl0lharry said:
Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.
Click to expand...
Click to collapse
dirtyl0lharry said:
Hi everyone!
First of all, forgive me for all my noobish mistakes as I have never had a HTC branded phone.
I'm about to buy this phone for a quite decent price and use it as my main and daily driver so before paying I want to know some basic things beforehand.
My main point is to get the rom "ViperOne" working in the M9 with root as I want the best performance from stock HTC firmware and because I need their drivers to be as good as possible ( sound wise).
I have already read the entire OP on the thread rom of ViperOne and I haven't seen a word about S-on/off so I'm guessing that I will not have to mess around with that kind of security right?
So to sum up things, will I need S-Off for this?
-Custom Recovery (twrp)
-ViperOne rom with root.
-Maybe installing another kernel over ViperOne.
-Thermal (software) mod.
-Audio mods.
Thanks everyone by advance.
Click to expand...
Click to collapse
You don't need s-off but it is HIGHLY RECOMMENDED to do so if you're rooting the device and messing with roms. It gives that extra level of recovering the device should you cabbage it.
This but is a slight education into custom roms and why "I" believe you shouldn't do it on ANY device:
Custom roms/firmwares are built using "open source" code. Stock roms/firmwares are built using "proprietary" code. "proprietary" code is code that is specifically written for 'x' device by a team of software engineers using "proprietary" software and hardware specifically built for 'x' brand. For example, htc have their own stuff and samsung have theirs, so on and so forth. This makes the software "married/tailor made" to the hardware so it comes as optimised as it can possibly be while weighing in factors of carrier "bloatware". No-one wants to lose a customer because of a device that is inherently slow. No-one will buy a device that is inherently slow.
Then you have custom roms and firmware. Because proprietary code is private and not for the public domain, this "open source code" is more or less "trial and error" process to get all the features of a rom or firmware to run efficiently and effectively. This results in non optimised bad code, bugs, long processes, excess code and therefore "CAN" be slower than stock roms. Couple this with deodexed and it'll bog the device down in no time.
So as you can see, I don't really like custom roms or firmware just for the fact it is no faster or no better than the software that came with the device in the first place. It was designed specifically.
My advice is to leave the phone stock rooted and s-off if you MUST have them. Otherwise don't touch it at all and continue to get updates as they are released with no hassle!.
Beamed in by telepathy.
I need to correct some of the information that got posted previously in this thread.
First of all: There are only custom roms but no custom firmwares for HTC devices (c.f. the difference between rom and firmware).
Second: S-OFF increases the risk of a hard-brick dramatically since it removes security checks of the phone (c.f. this article, the 5th post/the first page of Sneakyghost's firmware thread and the article that I already linked above). S-ON phones will refuse to accept broken files (e.g. RUUs that got corrupted due to a bad download). A phone with S-OFF on the other hand will get flashed with such a broken file and you won't get notified with any error outputs. Another example are those NoRedText aboots which remove the read warning that appears during the boot if the bootloader got unlocked. You can only flash them with S-OFF but if the hex edits didn't get executed correctly this can actually lead to unrecoverable damages.
Don't get me wrong. I'm using a S-OFF phone, too. However, you need to be aware of the risks and that you don't need S-OFF for recovering a phone. Keeping a RUU at hand for your current firmware version (if one exists) or at least a TWRP backup of the stock rom is more than enough. Damages that can't get repaired with either a RUU or a backup can't get repaired with S-OFF, either, in most of the cases.
Third: You need to differentiate between stock rom based custom roms (e.g. ViperOne or ICE) and those custom roms that are developed from source (those are the roms that shivadow mentioned in his post - e.g. Lineage or Resurrection Remix).
Those roms that are based on the stock rom deliver the same perfomance (or maybe an almost not noticeable better/worse performance) than the stock rom does. There are no differences between the core of these roms and the stock rom. (On the other hands this means that bugs of the stock rom are present in these roms, as well.) Therefore the performance differences are minimalistic. However, you don't flash such roms due to their performance differences (in comparison with the stock rom) but due to the additional features that they provide on top of the stock rom experience.
Causes for disadvantages of the other group of custom roms already got explained by shivadow in his post. A perfect example is the bad perfomance of HTC's cameras (the hardware of the phones not the app) on CM/Lineage roms. Nevertheless, I've never seen an HTC phone being incredibly slower on a custom rom than it was on the stock rom. My One S for example is much snappier on Lineage 14.1 than it would be on its android 4.1.1 stock rom and its battery is lasting much longer (well, android 7 has way more battery optimizations than android 4.1.1 so that isn't such a surprise). The only thing that I can complain about is (as mentioned before) the picture quality of the camera.
In other words, it's not always black and white. The best advice that I can give is to test all roms that are available and to use that custom/stock rom that suits your needs best.
Fourth and last: The M9 is more than two years old. HTC normally doesn't support any phone longer than this time period. There probably won't be any more updates than the nougat updates for those SKUs that haven't received firmware 4.x, yet.
TL;DR: What got written in post #2.
I tried to generalise, thats why i mentioned custom firmwares AND roms as some devices have custom firmware, rather than custom roms. Some have both, some have none.
Absolutely right that s-off is a double edged sword that you don't really want to fall on so I highly recommend that it is best to keep the device as stock but if you must root it it's worth s-off. I've seen plenty of posts for devices being screwed regardless of s-off. Also don't you need s-off to be able to restore your system backup from twrp?.
THE only reason I rooted my phone is to block "intrusive" ads. I don't want ads on my homescreen, lockscreen or really anything but apps that are good enough to warrant being paid for their efforts. Now that there is an abundance of adblocking software that no longer requires root I have absolutely no reason to keep my phone modded. I'd flash back to stock but my luck says I'll f**k the phone beyond recognition. It'll probably burn my house down, crash my car and kill my dog too!.
Nowadays root isn't necessary if you're not a dev. Thats the point I'm trying to get across!.
Beamed in by telepathy.
shivadow said:
Also don't you need s-off to be able to restore your system backup from twrp?
Click to expand...
Click to collapse
No, you don't (and never did). It doesn't make any sense to S-OFF the phone just because you can if you don't need it for any of the purposes that are mentioned in the articles/posts that I linked in my last post. It only highers the risk of bricks due to what I wrote in my last post.
And there are other uses for custom roms/root aside from ad blocking but that would be an off-topic discussion in this thread.
Sent from my HTC One M9 using XDA Labs
@Flippy498 @shivadow thank you guys for all the links and the extra informations. I really appreciate it since there are things about HTC that I haven't seen on any other brands.
To get things clearer, since my Moto G XT1039 is getting old ( low performance and battery barely keeps up with the day) and I'm really into music and sound (spotify premium and lots of flacs) and a Fiio X7 android based mp4 is too expensive, I wanted to get a top sound-chip phone, actually, a phone with a top Digital to Analogic Converter.
Of course I do know that if I want to use all the power and features that the M9 makes for its sound, I need to be on stock firmware because of the drivers. I'm guessing that the audio behaves like the camera once using and AOSP based rom ( LOS, Slim, RRemix...) getting worse.
Thats why I want this phone, it basically is much more powerful than my Moto G SD400, it has way better camera, it has a 64bit SoC and official Nougat update and I'll end up with a great DAP on my pocket to use with Spotify.
As I said, I like to get everything as minimal as possible, I hate when the home screen is full of icons and widgets, I hate having lots of icons and indicatos on the status bar, I hate having all sensor toggled on ( gpu, nfc, bluetooth...), thats why I was looking for a stock rom that let me custom all the things to keep it as minimal as possible.
If you know any other updated, stock based rom, just let me know and link it to me as I'll disable as many things as I can to get extra battery on the phone. Yes, you can guess it, even on battery saving mode, the M9 would beat the hell out of the Moto G, so I'm giving up on everything but the sound, just to get more battery time.
I hope you can understand me now.
Is it possible to have app stock like
\system\priv-app\SamsungCamera3.apk or VoiceNote4T.apk in CM13 or 14.x ??
Which \lib\ should I get ?
(thank you)
maxnuk said:
Is it possible to have app stock like
\system\priv-app\SamsungCamera3.apk or VoiceNote4T.apk in CM13 or 14.x ??
Which \lib\ should I get ?
(thank you)
Click to expand...
Click to collapse
Only if they are not dependent upon the touchwiz framework. For example samsungs internet browser can be installed on any device (example of non touchwiz dependent app) where as gear vr only works on samsung roms (touchwiz dependency) . It wont hurt to try you will just get non functional app or fc. NOTE!!!! I STTONGLY SUGGEST NOT FLASHING ANYTHING ANDROID IS DEPENDENT UPON FOR BOOT OR TOUCHSCREEN FUNCTIONALITY (SYSTEM UI, documents ui....leave anything with ui in package name alone. A phone without the ability to be interacted with would seriously suck. Obviously backup before trying system apps ....the camera isnt going to work ....im doubting voice note will either, but i havent tried either (the cam im certain wont work we have been looking for a working one since march)
I have an old T-Mo S4 on 4.something and would like to play with some custom ROMs. I see that there are several ROMs but am not sure which one to start on.
What's the cleanest, most compatible, stock-like ROM for the S4? Preferably Android 7.x or newer.
Additionally, is there a simple way of reverting back to an official T-Mobile ROM?
I went with lineage, used it for a couple of phones. It's currently in active development, root is optional so I think safetynet is not an issue. I think a couple of other ROMs are based on lineage, so I just stick with them.
As for reverting back I don't know. I had to download stock for an old phone and flash back, this time I tried backing up stock, but didn't back up stock recovery, didn't think of it and not sure if I can. I don't know if my backup of stock will work if I try to flash back. Still pretty new to all of this, or maybe not new so much as I'm not a developer and I'm trying to follow as best I can.
besweeet said:
I have an old T-Mo S4 on 4.something and would like to play with some custom ROMs. I see that there are several ROMs but am not sure which one to start on.
Click to expand...
Click to collapse
I flashed AlaskaLinuxUser's [ROM][7.1.1] SlimRoms N [jfltetmo] build on my bone-stock SGH-M919 a week ago. It's my daily driver, so I'm glad the 7.1.1 Slimroms ROM has proven to be lean and stable.
It carries the same SGH-M919 model number so IR blaster apps are available.
It is not rooted, so corporate sector apps don't have a cow over security.
It is easily rooted using the recover-flashable SuperSU zip, and easily unrooted inside the SuperSU app.
Portable Hotspot works well, although only in the 2.4GHz band.
Media players are absent (slim indeed), so I had to download AOSP Music+ etc.
Wi-Fi Calling does not work :crying: due to not having T-Mo's proprietary app.
TWRP can backup and restore the whole phone using an SD card. You'll need around 7GB free on the card.
snarkbait said:
Wi-Fi Calling does not work :crying: due to not having T-Mo's proprietary app.
Click to expand...
Click to collapse
Have you attempted to manually get Wi-Fi Calling working? There are plenty of stock devices - the Moto G6 for example - where Wi-Fi Calling works.