Develop Bugs

Light sensor level mod - no dev?

Hello guys, I've made the question, but the Q&A section is not very visited so...
http://forum.xda-developers.com/showthread.php?t=776871
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz

+1 really love to have one

casca said:
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz
Click to expand...
Click to collapse
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.

+1 I would love to see this as well.

martino2k6 said:
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.
Click to expand...
Click to collapse
you were faster than me searching, i was out lunching and haven't saw the topic reply e-mail
if you need assistance on testing, just PM me or let me know at the topic.
It would be nice to have this working, it's so annoying...
Why the f*ck do they include a light sensor if it doesn't work properly?!even after releasing fixes!?lol
Although I think I might know the answer...
"OK, so we gave them the hardware with buggy software to keep them busy...let them(users) figure out a fix, and this way we have time to develop some even nicer phones..."

The main problem here is that since we don't have HTC Sense sources, as they are proprietary, we can't modify system settings with an application which doesn't run as part of the system.
My understanding therefore is that this can be done in two ways:
1) Writing a kernel module which sets the appropriate/specified values on boot (I don't have enough experience to do that) or modifying the default kernel values.
2) Modify values in /sys (wherever they may be hiding) which will be reset any time you reboot, and also may get overwritten by the system at will.
That's my limited understanding anyway. If anyone would like to shed more light on this then please feel free to, or any other ways how this could be achieved...

Moved to Q&A. Please don't post question threads in Development.

fair enough
could we simply start an "official light sensor level developement for sense UI" thread or something like that ?

+1 guys we really neeeed that **** ;p
tks for your work !

[APP] Call Master - Need some Epic testers please!

Hi everyone! Thank you for your help in getting CM up to a flawless standard! We are now almost ready to deploy CM 1.5 - it will include MMS blocking, Class0 auto replies and many other new and very cool features.
We need your help now to iron out any remaining bugs before we embark on a daemon rebuild. Please download the app from the market and get testing! Here are the issues we want to address specifically:
- If you have problems regaining 3G after the telephony restart. This should have been fixed. If not, please try "Slow radio restart" in Debugging and report your results!
- Issues moving list priorities on Light or Dark theme. Again, if you have issues, please switch to the other theme, try again and then report back.
- Notification color schemes. We are interested if the new notifications comply with the majority of frameworks.
Thank you in advance for all your great work, this ultra-awesome app is as much a child of yours as it is of ours
-----------------------------------------------------------------------------------------------------------------------------
The most complete call and SMS management app on Android
Call Master is the most advanced call and text message firewall available for Android. With unique, powerful features and the proven reliability
of our root telephony daemon under the hood, this application is targeted at advanced users and professionals searching for an enterprise
quality solution that guarantees absolute stability.
If you find Call Master too complicated but like the power of its root telephony daemon, please have a look at our other call management app,
Root Call Blocker. It works just as effectively and may suit your needs better.
Advantages:
★ Blocked calls will never go through
★ Your screen will never turn on
★ Private call and SMS sandbox with log sweeper
★ Full password protection
★ Route message content to other numbers
★ Powerful widget
Features:
☆ Ultra flexible list creation
☆ Seven reject methods
☆ Filter SMS by content
☆ Automatic text routing and replies
☆ Regular expression and wildcard filters
☆ Custom notifications
☆ Backup encryption and password protection
☆ Powerful logging and sorting system
☆ Number testing
☆ Independent contact library for total privacy
☆ Profile scheduling
☆ Light and dark themes
Market Link: https://market.android.com/details?id=fahrbot.apps.blacklist&feature=search_result
This is a fully functional application. However, after a 24 hour demo period it will start nagging you to buy the Key, which will remove all nag
screens and timeouts from the interface. The nag screens are pretty light though, so users who dont want to spend can live with them.
Screens - VIEW GALLERY

Working great so far on EL13 and the only thing I wish you could do is block all numbers from a specific area code. I keep getting random calls from 503 numbers and its a different number each time so it's hard to catch them all.
If there is a way to do so please let me know and I'll give it a shot.
---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------
Please explain the difference between this and Root Call Blocker that you also developed. They seem like the same thing to me.

ssconceptz said:
Working great so far on EL13 and the only thing I wish you could do is block all numbers from a specific area code. I keep getting random calls from 503 numbers and its a different number each time so it's hard to catch them all.
If there is a way to do so please let me know and I'll give it a shot.
---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------
Please explain the difference between this and Root Call Blocker that you also developed. They seem like the same thing to me.
Click to expand...
Click to collapse
I know in root call blocker you can tell it how many digits to compare when it blocks a call/text.
For example you want to block calls from the 503 area code you'd tell it to only compare 3 or 4 digits and enter 503 as the ones to compare. It starts comparing numbers starting with the area code first (at least from what I can tell).
EDIT: Here's what the difference in the two is.
Route message content to other numbers (don't think this is in RCB, then again I don't have a need for it so I wouldn't know)
Seven reject methods (RCB has only 3 I think)
Filter SMS by content
Regular expression and wildcard filters
Backup encryption and password protection (don't think RCB has encryption)
Number testing
Independent contact library for total privacy

ssconceptz said:
Working great so far on EL13 and the only thing I wish you could do is block all numbers from a specific area code. I keep getting random calls from 503 numbers and its a different number each time so it's hard to catch them all.
If there is a way to do so please let me know and I'll give it a shot.
---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------
Please explain the difference between this and Root Call Blocker that you also developed. They seem like the same thing to me.
Click to expand...
Click to collapse
The way to block area codes it using wildcards and has nothing to do with what the guy above said. The two wildcards are * (any number of digits) and # (single digit). So to block everyone in France you add #33* as a number. Its all in the help mate.
Regarding differences. There are too many to name. They are completely different and if you dont understand wildcards i suggest you stick to RCB, it much simpler.
Now, lets please get back to the issue i described above. Thanks!

So I would use #503* to block all 503 area codes?

Let me break it down for you:
The first symbol in any international call is +
France has an area code: 33
Then after +33 come lots of other numbers like this: +33XXXXXXXXXXX
So if * is any number of characters and # is any single character
# is the plus sign and * is all the characters after 33: #33*
I dont know about your number - does it start with a letter other than 5?

ok this I'm going to have to play with.

Thanks, be sure to send logs if you have issues!

I been user since root call blocker. Trialed and bought call master. It killed my data after every reboot and randomly. Went nuts thinking I was getting LoS till I removed call master and it went away. I will re install app and help out.

One of the numbers I had on the block list just called me and it didn't block it.

ssconceptz said:
Working great so far on EL13 and the only thing I wish you could do is block all numbers from a specific area code. I keep getting random calls from 503 numbers and its a different number each time so it's hard to catch them all.
If there is a way to do so please let me know and I'll give it a shot.
---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------
Please explain the difference between this and Root Call Blocker that you also developed. They seem like the same thing to me.
Click to expand...
Click to collapse
Hey ss.....what rom are you running?
I tried to get caulks rom 1.94 to run with ACS ICS Theme....and the phones goes nuts !! constant bootloops!! at first I thought it was the combination of call master with this particular rom and theme....but im starting to think it is the rom and theme itself causing the extreme instability.

I'll help test! I LOVE new apps. Will report back my findings both good and bad.
Regards,
rast4man

so far UnNamed 2.0.1 with EL26 modem and it's working fine no issues as of yet.

Most of the time I saw issues was after a reboot. Everything looked fine until you tried to make a call. Then it said no mobile data, radio would restart and then things were fine until next reboot.

bsg411 said:
Hey ss.....what rom are you running?
I tried to get caulks rom 1.94 to run with ACS ICS Theme....and the phones goes nuts !! constant bootloops!! at first I thought it was the combination of call master with this particular rom and theme....but im starting to think it is the rom and theme itself causing the extreme instability.
Click to expand...
Click to collapse
I take it youre the guy that didnt believe us when we told you that CM cant possibly be causing BOOT LOOPS
HappyFillmore said:
Most of the time I saw issues was after a reboot. Everything looked fine until you tried to make a call. Then it said no mobile data, radio would restart and then things were fine until next reboot.
Click to expand...
Click to collapse
So wait. Everything is fine after boot until you try to make a call? That doesnt sound right...

bsg411 said:
Hey ss.....what rom are you running?
I tried to get caulks rom 1.94 to run with ACS ICS Theme....and the phones goes nuts !! constant bootloops!! at first I thought it was the combination of call master with this particular rom and theme....but im starting to think it is the rom and theme itself causing the extreme instability.
Click to expand...
Click to collapse
Maybe it is because the ICS theme is EL13.
Sent from my SPH-D710 using xda premium

Yeah...I'm the guy....it was the phone itself....I returned it and got a new one and everything works fine now....Including CM. Great app.....just wish it had a "built-in" private sms/mms box.....because u refused to add it to cm .....I'm left running 2 call block apps ....yours and extreme call blocker invisible. Nevertheless....still an amazing app!

Mate, we already have a private inbox. Use the Privatize action. The only difference is that its virtual.
That means that you actually converse through your app of choice, but a few seconds later the messages and call records are moved to the CM log, effectively accomplishing exactly what you want.
We also have a manual log sweeper (long-press on a list and pick "sweep system logs").

Updated OP - impressions please!!!

OH wow - thanks for the sale!!! All you apps only $2?!? How long for?

I'm glad to finaly see some dev support.... but...

There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).

sp00nix said:
There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).
Click to expand...
Click to collapse
Well first of all what do you term as slow ? Samsung gave us ICS in 8 months with major bugs, withdrew it and then released it again after 2 months. Whereas the devs here had already resolved those bugs.
Again CM10 is a tough one as this is the only device with CM10. The target was end of the year but look at it we already have CM10.1 as well. So the devs here are faster than the team at Samsung who get paid for it..
As the base is the same drivers and source written for CM10, all the ROMs based on it will have the same bugs.
GPS and camera are no more an issue. I've been using the camera on my CAMP rom and no issues. Also past 2 days I've driven for 600 kms and no issues with GPS and everytime it locks under 30 secs and works very well.
For me the only major bugs left are
1. Keyboard backlight - known solution
2. Sym key - known solution
Rothorick is working on the above two and will surely come up with a fix soon. The term half baked is not something you can use for ROMs being used as daily drivers!!!
Sent from my SGH-I927

Just be glad we get anything at all. We only have one main dev and only a few others helping the process. These roms WILL get finnished but only in due time. Just take some time to relax and be patient. I have faith in dman and all his hard work is greatly appreciated here. Its the holidays let dman have his time to himself.
Sent from my SGH-I927 using xda premium

sp00nix said:
There seem to be lots of ROM options coming to fruition, but they all seem to be half baked and development is slow. Why not have the Dev's team up and make one awesome ROM? It is getting hard to choose between things like a working GPS or a working camera(for example only).
Click to expand...
Click to collapse
Errrr..... current CM10.1 has everything but bluetooth and the keyboard backlight. And dman is cracking the whip on bluetooth right now.
Also, the way you word the question betrays a misunderstanding in the process. Most of the ROM developers don't have the knowledge and experience to troubleshoot hardware compatibility problems. We have dman, that's about it. The rest of us, at best, only know enough to gesture furtively in the correct direction or unearth an important path or config file. So, fixes are implemented by dman and rolled out in his sources and ROMs, and his sources are then used by other people to build their ROMs.
---------- Post added at 02:38 PM ---------- Previous post was at 02:34 PM ----------
ninthsense said:
For me the only major bugs left are
1. Keyboard backlight - known solution
2. Sym key - known solution
Rothorick is working on the above two and will surely come up with a fix soon. The term half baked is not something you can use for ROMs being used as daily drivers!!!
Click to expand...
Click to collapse
You give me way too much credit. I only figured out half of the keyboard backlight problem -- the other half necessarily must come from dman as I don't know where to begin on getting the Android core to poke the sysfs.
As for the keyboard, we have a kludge for the Sym key. I'm working on a proper solution, as well as a fix for the voice search and dotcom keys, but in both cases, because we need changes in core classes, it's more a matter of open-source politics than technical troubleshooting.

roothorick said:
---------- Post added at 02:38 PM ---------- Previous post was at 02:34 PM ----------
[/COLOR]
You give me way too much credit. I only figured out half of the keyboard backlight problem -- the other half necessarily must come from dman as I don't know where to begin on getting the Android core to poke the sysfs.
As for the keyboard, we have a kludge for the Sym key. I'm working on a proper solution, as well as a fix for the voice search and dotcom keys, but in both cases, because we need changes in core classes, it's more a matter of open-source politics than technical troubleshooting.
Click to expand...
Click to collapse
Yup, the special hardware keys are a issue in CM on every slider phone. Hope you get a proper solution to this, so we don't have to fool around with framework-res and keyboard files

ninthsense said:
Yup, the special hardware keys are a issue in CM on every slider phone. Hope you get a proper solution to this, so we don't have to fool around with framework-res and keyboard files
Click to expand...
Click to collapse
It literally comes down to submitting patches to CyanogenMod and AOSP and hoping they see the need. We could just make builds with the patch, but we can't call them CyanogenMod or AOSP then.
Could we compile a list of devices that need extra keycodes? It'd definitely bolster our case to say "these 42 phones are directly affected by the issue solved by this patch", plus I can be more thorough.

roothorick said:
It literally comes down to submitting patches to CyanogenMod and AOSP and hoping they see the need. We could just make builds with the patch, but we can't call them CyanogenMod or AOSP then.
Could we compile a list of devices that need extra keycodes? It'd definitely bolster our case to say "these 42 phones are directly affected by the issue solved by this patch", plus I can be more thorough.
Click to expand...
Click to collapse
Can you elaborate on the the code change you are planning to submit. We can still have a patch on top of CM or AOSP, just like we have so many proprietary files from samsung.
Sent from my SGH-I927 using xda app-developers app

ninthsense said:
Can you elaborate on the the code change you are planning to submit. We can still have a patch on top of CM or AOSP, just like we have so many proprietary files from samsung.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
We need to change certain core classes like KeyEvent and a few others (there's a list in the comments in KeyEvent.java) as well as a few other places to connect the keycodes to their correct behavior. And it needs to be done in a way that works globally for all phones, not just the Glide. Which is, more than anything, a matter of convincing devs bigger than any of us that we know what we're doing, we didn't break anything, and it's a necessary change.

[ROM] MIUI Port

This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409

Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?

If you want mae some cool port, i thikn sense rom is good candidate...

Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far

Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.

Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there

Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.

MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support

uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom

I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.

MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?

jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video

uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?

jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.

uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.

justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.

good luck

I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.

FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).

MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:

Remove Sms hour limit (and other limits) for Android 6 ( MM )

I have a problem when sending many sms. I get that warning from Android, on which I have to choose if I allow or decline . By default I think the limit is for 30 sms/hours
How can I solve this for Android 6 Marshmallow?
I know there are some tricks for other versions of Android, but for Android 6 does anyone succeeded in some way to disable the sms hour limit?
Thank you

no one?

+1

+1

did someone find a way, or heard about a way or has any ideas? Still, after 3 months, I am struggling with this. I just found the CM based ROMS can increase the limit, but no one can disabled it...

eltigre4jc said:
did someone find a way, or heard about a way or has any ideas? Still, after 3 months, I am struggling with this. I just found the CM based ROMS can increase the limit, but no one can disabled it...
Click to expand...
Click to collapse
In RR I can disable that limit completely.

steadfasterX said:
In RR I can disable that limit completely.
Click to expand...
Click to collapse
Great... !
I asked once in the CM forums, and got some very unkind answers.... I was hoping someone (maybe developers from the CM) to find a way or explain how can the limit be removed in every 6.0 ROM. Maybe something like in the KitKat version (go and edit some .db files, add some variables). In RR and other CM based ROM's , you can only select predefined values for the limit, but what is done in the background... few people know...
Maybe someone, someday, will find a way....

eltigre4jc said:
Great... !
I asked once in the CM forums, and got some very unkind answers.... I was hoping someone (maybe developers from the CM) to find a way or explain how can the limit be removed in every 6.0 ROM. Maybe something like in the KitKat version (go and edit some .db files, add some variables). In RR and other CM based ROM's , you can only select predefined values for the limit, but what is done in the background... few people know...
Maybe someone, someday, will find a way....
Click to expand...
Click to collapse
Ok I had done a little research for you and I think I have found what you asked for:
https://github.com/CyanogenMod/andr...ternal/telephony/SmsUsageMonitor.java#L59-L78
As you can see this is an internal telephony setting which afaik cannot be adjusted by just modding a file. It has to be implemented in the ROM.
some apps seem to bypass that limit somehow but that seems to be another story. People reported that removing the preinstalled SMS app had also removed the limitations for them but well you could give it a try but I do not think that this will solve it.
(click at thanks on this post - if my answer has helped you)
.

steadfasterX said:
Ok I had done a little research for you and I think I have found what you asked for:
https://github.com/CyanogenMod/andr...ternal/telephony/SmsUsageMonitor.java#L59-L78
As you can see this is an internal telephony setting which afaik cannot be adjusted by just modding a file. It has to be implemented in the ROM.
some apps seem to bypass that limit somehow but that seems to be another story. People reported that removing the preinstalled SMS app had also removed the limitations for them but well you could give it a try but I do not think that this will solve it.
(click at thanks on this post - if my answer has helped you)
.
Click to expand...
Click to collapse
Thank you so much... At least now is more clear. I am using Textra and I froze the default SMS app. But still the limit was there. I can only hope someone will implement this, mayve in g4 TweakBox or and Xposed module.
ANyway, if you know a workaround or a possible solution, I will be glad to test...

eltigre4jc said:
Thank you so much... At least now is more clear. I am using Textra and I froze the default SMS app. But still the limit was there. I can only hope someone will implement this, mayve in g4 TweakBox or and Xposed module.
ANyway, if you know a workaround or a possible solution, I will be glad to test...
Click to expand...
Click to collapse
freeze is not remove.
try to remove it completely but do a nandroid backup before!!