Related
Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
DeMar27 said:
Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
Click to expand...
Click to collapse
Hi Demar, I'm currently on GR4, but it should be the same on TP2.
I just tested with my own setup, I set the wi-fi channel on the router to channel 13, and the phone was unable to connect.
Then I changed the property "ro.wifi.channels" in build.prop to 13. After a reboot it connected fine.
So it seems that's all you need to do, either edit or add the line
"ro.wifi.channels=14"
to your build.prop.
Yeah. I know this. I tried, but without results..
DeMar27 said:
Yeah. I know this. I tried, but without results..
Click to expand...
Click to collapse
Which kernel are you using? I'm on HP-RC4.
Problem solved.
I'm not sure with what ?
I changed following:
ro.product.locale.region=EU
ro.wifi.channels=14
And installed some script that I found on forum
No I can choose regulatory domain
Wifi channels enable for both 11g/11n networks
DeMar27 said:
Problem solved.
... installed some script that I found on forum
Click to expand...
Click to collapse
Hmm... What script do you mean?
Anyway, to enable last (14) channel for .11g, without the script,
you need to set "wifi_country_code=JP" in the "secure" table in the following database:
"/data/data/com.android.providers.settings/databases/settings.db".
(It may be easily done with RootExplorer and SQLite editor installed).
Also, it may help for 5GHz .11n too, by default (for USA) very few channels are available,
Most channels in .11n become active with EU code in the field above.
And, there is no need to reboot the phone after change - just switch WiFi off/on!
alanber said:
"/data/data/com.android.providers.settings/databases/settings.db"
Click to expand...
Click to collapse
In my case there is no .db file
But it's a Samsung Galaxy A5 (2017) of course...
SebastianFM has kindly agreed to provide support to fix issues.
That i think is a fantastic news
so please show your appreciation by thanking for the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM
Click to expand...
Click to collapse
I REQUEST/ENCOURAGE ANY DEV OUT THERE WHO WOULD LIKE TO TAKE OVER
OR START A FRESH TO BUILD GB-SENSE ROM PLEASE DO SO,
THIS THREAD IS MAINLY FOR INFORMATION PURPOSE
Click to expand...
Click to collapse
warning/disclaimer:
I am not maintaining this ROM, i have only transported this from SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
initial attempt was on SenseonFire ROM from wildfire
please don't bother this thread with trivial questions
this ROM is only for testing purpose and inspiration for further development only
I started this, with intention of porting the ROM, only to realize that I am not smart enough to fix most things.
I am not claiming to be dev as i am not, so posting the info for you to proceed or dump the project.
WIP <- working in pause (not work in progress)
I thank
SebastianFM for the first porting, which made possible most of the other device ROMs SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
all those involved in SenseonFire ROM project on wildfire especially VigiDroid,
and Arco for building an awesome kernel and nFinityGB v1.13 ROM for tattoo and some of the files were taken from this ROM
and dsixda's Android Kitchen
Click to expand...
Click to collapse
The main reason I have opened this thread is, to make you aware of the promising future out there for sense lovers using tattoo
and sow some seeds of inspiration for a dev out there who could fix this for us.
What i did
I took the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM used dsixda's Android Kitchen utility to transport and then adjusted few libs and binaries to get the phone started
Used Arco's 2.6.35.14 kernel and files from his nFinityGB v1.13 ROM
and added Robot font from following thread http://forum.xda-developers.com/showthread.php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
Click to expand...
Click to collapse
things like gps, fm and camera are not working on tattoo, many apps need resizing or font size needs reducing.
when i did benchmarking using cf-bench apk, the score i got was more than 500 close twice to what i got with tatfroyosense. Benchmark done at 633 Mhz max cpu
rom link and snapshots
Download links
SFM port version 1.2.1
mediafire
4shared
Changelog
V1.2.1
Pooled all patches together and few minor changes
V1.2
Few apks resized
ROM is by default Overclocked
framework symlinked from cache partition
wipe cache, data before flashing the ROM
First boot takes about 5-10 mins
Main issues:
GPS
Camera
FM
Media player sound OK - video is white
no notification lights (but button lights OK)
Battery drain - if wifi on
and other issues from user (??)
old versions
SFMportv1.2
http://www.mediafire.com/?uzutj2tura75oyr
SFMportv1.1
http://www.megaupload.com/?d=KXLUD91K
SenseonFire port link
http://www.megaupload.com/?d=UYZ4V0WJ
the rom has edify scripting and is unsigned, could be installed with clockworkmod recovery
Click to expand...
Click to collapse
This is cool. I never expected Tattoo to run anything heavy like this.
Feeling proud of you, man! With tears in my eyes.
Sent from my HTC HD2 with my fast fingers.
Waiting for news!!
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
and about camera and videorecorder, u can get the drivers from CM7 and merge with this. For FM, u could get get drivers from CM7 and replace the HTC FM app with the one from CodeAurora or MIUI.
I am interested to help. But it seems I have got some other priorities to attend to. I will be free after April 2012. Then I will brush up my C++ skills and see if I can help u all.
...
too bad,this rom would be perfect if bt, gps, wifi, camera would working on tattoo...
sunitknandi said:
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
Click to expand...
Click to collapse
I dont think this is issues with old and new kernel, they all had access points as tiwlan0 (fyodor, ralle.gade and arco).
So far to my understanding it is device specific (see below).
Dexter seems to have tweaked the module and wpa_supplicant from ralle.gade's kernel to work with Froyo, i dont know what was changed. to get wifi working
EDIT: eth0 limitation is with hardware used in the device
Devices like: Wildfire, Wildfire S, Icon-G and Explorer -have their the access point setup as eth0 and they all have broadcom chip
while Tattoo, Magic and Hero -have tiwlan0 as the access point and they all seem to TI chip
in that case, lets ask dexter. he can help.
sunitknandi said:
in that case, lets ask dexter. he can help.
Click to expand...
Click to collapse
I asked him, he still hasn't responded...
P.S.
i get this from the logcat: " wifi_load_driver end error 2" and from dmesg i get something like: "firmware_path unknown value"
I researched and foundout that the deire had similar problems, but they had a previously working dirver and just couldn't conect....
So that leaves me nowhere again... (sadface)
Few things that i have't mentioned earlier:
Following are the commands in wpa_supplicant script for tatfroyosense
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant.bin -Deth0 -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
As it is tiwlan0 interface in Arco's kernel, i have copied wlan_loader, wlan_cu, wpa_supplicant, wpa_cli binaries from nFinityGB rom along with /system/etc/dhcpcd folder and the wifi module. (These are already in the ROM attached)
As some of you might have noticed:
module wont load at boot
so i have tried to execute following commands from shell (they are in the init.rc script except insmod of module)
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/firmware/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant -Dwext -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
module loads fine but then wlan_loader give following error
Code:
rtnl_open: Protocol not supported
Hello mate. Is it possible to provide a github repository with the code?
ntenisOT1948 said:
Hello mate. Is it possible to provide a github repository with the code?
Click to expand...
Click to collapse
I dont think HTC source code out there for sense andriod phones.
The time line for this ROM is as follows:
HTC Salsa was ported to Sapphire
http://forum.xda-developers.com/showthread.php?t=1025330
From Sapphire to wildfire
http://forum.xda-developers.com/showthread.php?t=1067868#13557996
wildfire then updated to this
http://forum.xda-developers.com/showthread.php?t=1269485
From above ROM to this ROM
Following files were taken from nFinityGB v1.13 ROM to this ROM
Code:
Filename Folder
wlan_loader system\bin
wpa_cli system\bin
wpa_supplicant system\bin
vold.fstab system\etc
dhcpcd.conf system\etc\dhcpcd
brf6300.bin system\etc\firmware
brf6350.bin system\etc\firmware
Fw1251r1c.bin system\etc\firmware
tiwlan.ini system\etc\wifi
wpa_supplicant.conf system\etc\wifi
Clockopia.ttf system\fonts
DroidSans-Bold.ttf system\fonts
DroidSans.ttf system\fonts
libwpa_client.so system\lib
copybit.bahamas.so system\lib\hw
gps.bahamas.so system\lib\hw
gps.goldfish.so system\lib\hw
gralloc.bahamas.so system\lib\hw
gralloc.default.so system\lib\hw
lights.bahamas.so system\lib\hw
sensors.bahamas.so system\lib\hw
sensors.goldfish.so system\lib\hw
wlan.ko system\lib\modules
bahamas-keypad.kcm.bin system\usr\keychars
bahamas-keypad.kl system\usr\keylayout
AVRCP.kl system\usr\keylayout
vim system\usr\share
colors system\usr\share\vim
filetype.vim system\usr\share\vim
ftoff.vim system\usr\share\vim
indent.vim system\usr\share\vim
indoff.vim system\usr\share\vim
scripts.vim system\usr\share\vim
blue.vim system\usr\share\vim\colors
darkblue.vim system\usr\share\vim\colors
default.vim system\usr\share\vim\colors
delek.vim system\usr\share\vim\colors
desert.vim system\usr\share\vim\colors
elflord.vim system\usr\share\vim\colors
evening.vim system\usr\share\vim\colors
koehler.vim system\usr\share\vim\colors
morning.vim system\usr\share\vim\colors
murphy.vim system\usr\share\vim\colors
pablo.vim system\usr\share\vim\colors
peachpuff.vim system\usr\share\vim\colors
ron.vim system\usr\share\vim\colors
shine.vim system\usr\share\vim\colors
slate.vim system\usr\share\vim\colors
torte.vim system\usr\share\vim\colors
zellner.vim system\usr\share\vim\colors
VoiceDialer.g2g system\usr\srec\config\en.us\grammars
wlan_cu system\xbin
Great news guys
I got wifi and bluetooth working
As i mentioned the history of the ROM in previous post,
It occured to me, may be i can start fresh from Sapphire ROM
So i went to the follwoing post and started with SFM 3.0.2
http://forum.xda-developers.com/showthread.php?t=1025330
and with rough porting i could get wifi and bluetooth working and i bet gps would also work.
you know it was quick and dirty port (huge size and bad layout),
now we can do proper port with relayout and resizing the framework and would be better ROM
Cool... Keep up the hard work. Once u finish the port, we can get someone to optimise it.
Have you updated the download link? Iwould like to have a look to graphics to know if I can do anything about them.
Edit: I can see you don't. But I'm going to start trying to resize some graphics as a practice for future.
2nd post updated with new rom port
some of the applications are not working and poor layout.
Alternative launcher like adw working fine
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
sense zero on tattoo
Now that i could port (transport) GB sense, i wanted to have a crack at sense zero (it was to decide which one would be best carry on)
so I did try port Hintay Zero 0.14 (Sense 3.5 Android 2.3.5)
and i could get it booted on Tattoo,
but have to set lcd density to 100, so that you can see launcher work.
But most of other things look decent if it is set to 120.
And you can see that layout and size are bad.
but i have to say it takes lot of memory and gets very slow.
framework moved to cache to make space in system.
takes 10 mins on first boot
here the link
http://www.megaupload.com/?d=X1B721BZ
and snapshots
GbermuG said:
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
sunitknandi said:
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
Click to expand...
Click to collapse
That's what I can understand using translators: they've tried it, and like it. They thik is smooth and powerfull, but ram memory is low. Someone is asking about Sense 3.0, but the tread is not updated, so they only tried SenseonFire (first port). Simply (as I said), they're waiting.
it seems that is working, tried it on 4.4.2, but no OAD support..
to enable it add the following line to android/system/device/motorola/omap4-common/common.mk
frameworks/native/data/etc/android.hardware.bluetooth_le.xml:system/etc/permissions/android.hardware.bluetooth_le.xml
next to
frameworks/native/data/etc/android.hardware.usb.host.xml:system/etc/permissions/android.hardware.usb.host.xml \
and (device specific) system/device/motorola/maserati/bluetooth/bdroid_buildcfg.h
#define BTA_DM_COD {0x1A, 0x01, 0x14}
#define BTIF_HF_SERVICES (BTA_HSP_SERVICE_MASK)
#define BTIF_HF_SERVICE_NAMES { BTIF_HSAG_SERVICE_NAME }
#define PAN_NAP_DISABLED TRUE
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE
after
#define BTM_DEF_LOCAL_NAME "Motorola Droid 4"
tried with new bluetooth firmware from https://github.com/TI-ECS/bt-firmware, is working but is not stable.
the default firmware is working well with the sensor tags
lucize said:
it seems that is working, tried it on 4.4.2, but no OAD support..
Click to expand...
Click to collapse
Great
I've just pushed your changes to my repositories, so they will be included in tomorrows nightly.
Merry Christmas,
Michael
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
lucize said:
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Click to expand...
Click to collapse
Ok, short gerrit crash-course
Configure your local git to commit with the name and email-address you want to be visible in public repositories
Create an account on http://review.cyanogenmod.org/
Upload an ssh public key there
Clone the repository you want to change with something like:
Code:
git clone ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common
(This is not necessary if you are working on a direct CM clone and have no other changes in your repository)
Make your changes, commit them
Push your changes to gerrit:
Code:
git push ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common HEAD:refs/for/cm-11.0
This will tell you an URL where your change is visible.
Go to that URL and add reviewers to your change. For example: Hashcode, David Hacker and probably me (Michael Gernoth)
If your change is acceptable, it will get merged into the CM repository
That's all, no great magic
For more info, have a look at: http://review.cyanogenmod.org/Documentation/user-upload.html
Best regards & thanks for your work,
Michael
lucize said:
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
Click to expand...
Click to collapse
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
bofis said:
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
Click to expand...
Click to collapse
is part of cm11, you can find it in /etc/firmware/
you can find it here
https://github.com/TI-ECS/bt-firmware/commits/master this is the history page where you can find various versions, but the last version from December won't load and the rest will not work with the headset (no sound)
htc one x has the same bluetooth chip and has a newer version of firmware, but the sound on headset will not work either, everything else seems to work
you can see the version at the beginning of the file, motorola has TI_P6_15.56
to update, turn bluetooth off, simply overwrite the file and the turn it on again.
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
guyincog said:
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
Click to expand...
Click to collapse
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
lucize said:
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
Click to expand...
Click to collapse
Thanks for the reply. I've got one, maybe I'll see if I can talk one of the builders for the Bionic will make a test build with the necessary common.mk change.
I apprciate the work on this, and the kernel update you've got in progress. Any extra features we can add to these old devices is a huge bonus.
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
bofis said:
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
Click to expand...
Click to collapse
it has the hardware support
http://www.aptx.com/product/motorola-razr-maxx-smartphone
but don't know about the rest of the things
This app has been heavily inspired by SabrWolfs [APP][ROOT] Touch screen fixer.
The app is supposed to at least temporarily improve the touch on the Oneplus one, making the device usable. I can't guarantee that it works for you, but it makes a big difference for me.
The app requires root, and executes the shell command cat /sys/class/input/input0/baseline_test every time the screen is turned on. It is not based on Tasker, but implemented as an ordinary app. The difference compared to Touch screen fixer, and the reason I made this app, is that the vibration is configurable. I initially implemented this app to be able to deactivate the vibration entirely, but since it actually takes a second or two to run the command and get touch working again, I found that I actually prefer a very brief vibration as feedback that the device is ready for use.
As usual with root apps, don’t forget to grant the app root access the first time it is started, otherwise it won’t work.
And as always, I can't take any responsibility if this app makes your house to burn down, your car to explode or your phone to overheat
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Gamm86 said:
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Click to expand...
Click to collapse
I'm using stock 12.0-YNG1TAS2I3, the latest offical CyanogenMod release. But, the same problem existed before as well, so it is not directly related to a specific ROM.
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
zodiaxe66 said:
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
Click to expand...
Click to collapse
Yes, this must be the first bug free app ever
let me try and giv u a result
As the result, i do feel different in touch screen. Much more sensitive
Thanks will try it
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Am using oxygen os from day 1 and never had suck issue.
Though i had some problem in cyanogenmod nightlies so reverted back to stock oxygenated n os
Sent from my A0001 using XDA Free mobile app
dxxvi said:
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Click to expand...
Click to collapse
The relevant part really just looks like this
Code:
public static int runTouchFixCommand()
{
int result = -1;
try {
Process p = Runtime.getRuntime().exec(new String[]{"su","-c","cat /sys/class/input/input0/baseline_test"});
result = p.waitFor();
} catch (IOException | InterruptedException e) {
e.printStackTrace();
}
return result;
}
The key here is that it is the /sys folder. It is not an ordinary filesystem but a virtual one used to communicate with different attached devices, in this case the synaptic touch driver.
See wikipedia for some further details: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#FHS_compliance
If I understand things correctly, reading baseline_test will run this code:
https://github.com/CyanogenMod/andr...s/input/touchscreen/synaptics_dsx_i2c.c#L1780
Which near the end does this "//step 5:reset touchpanel and reconfig the device".
Or it may just be magic
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Definitely works very well. I was using SabrWolf fix before this, thanks for the additional vibration duration option.
Unfortunately this app seems to be needed for CM12.1 as well. Fortunately it still works
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I haven't tested any CAF build (perhaps I should), but in the sultanxda case, I would guess this line in the description is to blame "Rewrote half of the Synaptics touchscreen driver (over 2500 lines of code modified; your touchscreen might work better)". The function my small app relies on (synaptics_rmi4_baseline_data in synaptics_dsx_i2c.c) is removed. So I'm afraid I can't get it to work there.
wrinkletit said:
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
Click to expand...
Click to collapse
I have worked a bit with xposed, but I don't really see any gain to use it for this purpose..?
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I have tried Sultans CM12 version, with the CAF kernel now, and my phone is working better then it ever have. No problem with the touch, so no need for this app, at least not for me.
Question for Kernel Devs, Re: Hotspot, DUN, "Carrier does not allow type 'dun'."
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
pbergonzi said:
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
Click to expand...
Click to collapse
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Dirk said:
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Click to expand...
Click to collapse
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
pbergonzi said:
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
Click to expand...
Click to collapse
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
nvertigo67 said:
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
Click to expand...
Click to collapse
I apologize for misunderstanding.
Thank you for the clarification and your efforts.
nvertigo67 said:
I've stated it's "more complecated"
Click to expand...
Click to collapse
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
pbergonzi said:
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
Click to expand...
Click to collapse
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
nvertigo67 said:
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
Click to expand...
Click to collapse
Yes, thank you.