Hello.
Have you ever tried to port Rom's from model with wifi ot model with 3g? Which files need to copy to make modem work?
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
kimshooter said:
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
Click to expand...
Click to collapse
Never go full retard.
kimshooter said:
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
Click to expand...
Click to collapse
So I take all the ROMs that are available for both WiFi and 3G model are made with pure magic then ? Hmmm..
Sent from my C6603 using xda premium
farstar7s said:
Hello.
Have you ever tried to port Rom's from model with wifi ot model with 3g? Which files need to copy to make modem work?
Click to expand...
Click to collapse
I believe any of tge general gyides fie porting (which you can avail by searching) is also applicable here, even if its not, trying won't hurt as nothing more than a soft brick can occur, afaik, even of anything goes wrong
khaytsus said:
Never go full retard.
Click to expand...
Click to collapse
LOL.
farstar7s said:
Which files need to copy to make modem work?
Click to expand...
Click to collapse
It's a little more involved than just simple file copying as to get it working fully requires changes to the framework-res to enable telephony in the android layer. Below are the changes you make to enable telephony on a rom if you building from AOSP sources but you can use apktool or similar programs to mod an existing rom ( I think these settings are found in the arrays.xml )
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
WHY? Changes these settings enables the Mobile Networks Option in the Settings
Then you'd need to copy the following files from a Nexus3g Stock Rom, Generally you try to match the build ID number to your target when copy system file however it shouldn't make a difference in the case of the Nexus7 because it's all Jellybean.
Code:
/system/bin/rild
/system/bin/pppd ( if it doesn't exist )
/system/lib/librilxgold-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
WHY? the rild ( radio interface daemon and it's supporting libraries ) handle the requests to and from the baseband processor the vendor specific implementation is in this case found librilxgold-ril.so. the permissions files lets the Android UI access the Radio Interface Layer ( through the rild ). pppd - some ril implementations rely on pppd to establish the data connection.
Add or change the following settings in your build.prop file
Code:
rild.libpath=/system/lib/libxgold-ril.so
rild.libargs=-d /dev/ttyACM0
WHY? This is the settings that the ril daemon will use when it auto starts - the name of the vendor library and libargs. The -d switch is the name of the device node that all that juicy 3G data flows.
Make sure the build.prop and any files you change have the correct permission set. Thats 0644 for non exectuable ( everything except stuff in /system/bin ) and 0755 for executable ( rild and pppd ) on some system pppd needs the superuser stickybit setting ( 6755 ) but that doesn't look like the case maybe google are using some off that magic that @leminhnguyen0703 speaks of or parhaps the vendor ril doesn't rely on it in this case
DEBUGGING
Use adb logcat -b radio to see what the RIL Stack is upto as standard logcat doesn't include this information
I think that pretty much covers it.
Reference : Android Platform Development Kit - Radio Interface Layer
@leminhnguyen0703 Now where did I put my wand? LOL
Thnx
trevd said:
LOL.
It's a little more involved than just simple file copying as to get it working fully requires changes to the framework-res to enable telephony in the android layer. Below are the changes you make to enable telephony on a rom if you building from AOSP sources but you can use apktool or similar programs to mod an existing rom ( I think these settings are found in the arrays.xml )
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
WHY? Changes these settings enables the Mobile Networks Option in the Settings
Then you'd need to copy the following files from a Nexus3g Stock Rom, Generally you try to match the build ID number to your target when copy system file however it shouldn't make a difference in the case of the Nexus7 because it's all Jellybean.
Code:
/system/bin/rild
/system/bin/pppd ( if it doesn't exist )
/system/lib/librilxgold-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
WHY? the rild ( radio interface daemon and it's supporting libraries ) handle the requests to and from the baseband processor the vendor specific implementation is in this case found librilxgold-ril.so. the permissions files lets the Android UI access the Radio Interface Layer ( through the rild ). pppd - some ril implementations rely on pppd to establish the data connection.
Add or change the following settings in your build.prop file
Code:
rild.libpath=/system/lib/libxgold-ril.so
rild.libargs=-d /dev/ttyACM0
WHY? This is the settings that the ril daemon will use when it auto starts - the name of the vendor library and libargs. The -d switch is the name of the device node that all that juicy 3G data flows.
Make sure the build.prop and any files you change have the correct permission set. Thats 0644 for non exectuable ( everything except stuff in /system/bin ) and 0755 for executable ( rild and pppd ) on some system pppd needs the superuser stickybit setting ( 6755 ) but that doesn't look like the case maybe google are using some off that magic that @leminhnguyen0703 speaks of or parhaps the vendor ril doesn't rely on it in this case
DEBUGGING
Use adb logcat -b radio to see what the RIL Stack is upto as standard logcat doesn't include this information
I think that pretty much covers it.
@leminhnguyen0703 Now where did I put my wand? LOL
Click to expand...
Click to collapse
Thank you. It show me right direction. I hope you won't get angry to me. I am actually Acer iconia a701's user. We have weak society. But acer iconia a700's auditory is bigger. There is same situation with 3g.
Now i get working Rom, Except icon of 3G,GSM and working Internet.
I don't get why all peoples thought dass there is no posibility to do it. It is easy enough if to know what to do. Thank you you helped me much.
farstar7s said:
Thank you. It show me right direction. I hope you won't get angry to me. I am actually Acer iconia a701's user. We have weak society. But acer iconia a700's auditory is bigger. There is same situation with 3g.
Now i get working Rom, Except icon of 3G,GSM and working Internet.
I don't get why all peoples thought dass there is no posibility to do it. It is easy enough if to know what to do. Thank you you helped me much.
Click to expand...
Click to collapse
Obviously there maybe be other hardware differences with the Acer in H/W but if you got a ported rom booting and just need the 3G going then you can use this method on pretty much every device provided you can source the RIL files etc, There also maybe some extra bits, like you need to make sure the modem device node has the correct permissions in ueventd.rc ( the N7 wifi model already has this set ), There's a couple of links in my sig regarding stuff I did to get Huawei Dongles working on various Devices. You might pickup some tips from there.
leminhnguyen0703 said:
So I take all the ROMs that are available for both WiFi and 3G model are made with pure magic then ? Hmmm..
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
BURN THE WITCHES OF WHOM THAT PORT!
Sent from my HTC One using xda premium
Related
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.
[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks
GSM USER INFORMATION FOR KEXEC ROM
It seems there is a lot of confusion about using the rom on GSM networks... false information about requiring build.props, flashing radios, etc. so I will give some general information...
EITHER METHOD; THE PHONE MUST BE UNLOCKED WITH EITHER AN UNLOCK CODE FROM VERIZON OR BOUGHT FROM A 3RD PARTY SOURCE.
FOR DROID 3 XT862 ONLY, XT860 REQUIRES A PATCH FOR RADIO DRIVERS.
UPDATE; ATTACHED PATCH TO THIS POST, UNTESTED BY ME, ASK OTHER USERS IN THE THREAD FOR SUPPORT, I DO NOT OWN AN XT860.
USING NON-US "FOREIGN" GSM NETWORKS
Radio;
Stock XT862 radio
build.prop;
Default included build.prop (Edit lines ro.mot.phonemode.vzwglobalphone=1 and ro.telephony.default_network=7 IF REQUIRED to ro.mot.phonemode.vzwglobalphone=0 and ro.telephony.default_network=3 respectively. )
MAY NOT BE REQUIRED TO EDIT THESE LINES
Required options;
Under Wireless & Networks section; UNCHECK Enable alt OEM and Enable Alternate getIMSI, then CHECK Enable World Phone and Enable GSM Signal.
Reboot the phone.
Back in the menu; select mobile network settings, change Network Mode to GSM/WCDMA, check/add/edit your APNs.
NO FLASHING/MODIFIED BUILD.PROP REQUIRED (except mentioned build.prop edits which are NOT required, just cosmetic, might not be needed)
USING US GSM NETWORKS (AT&T, T-MOBILE, Etc)
Radio;
XT883 radio (Baseband n_34.18.16s)
build.prop;
Edited build.prop attached to this post. (No editing required, remove .zip from the end)
Required options;
Same as above.
Follow instructions on flashing the radio here; http://forum.xda-developers.com/showthread.php?t=1406812
Use the radio img I uploaded here; http://www31.zippyshare.com/v/98608047/file.html (It's newer than provided in previous link)
Copy the attached build.prop (make sure to backup original) to /system and set permissions rw-r--r-- (644) remove .zip (it is not an actual zip)
MUST FLASH XT883 RADIO AND COPY BUILD.PROP, ELSE NO SIGNAL, PHONE NUMBER, BASEBAND, ETC.
Personally I use a Droid 3 XT862 on Straight Talk's SIM BYOP plan with an AT&T version SIM, I get HSPA 14.4 network and average ~5 to 5.50Mbps download speed. Only issues are known issues with the phone, everything radio related works flawless.
MMS ON GSM WORKS.
Just remember to include "mms" in the APN type, or as required by your carrier.
Just for information; If your data seems unstable, you can try my ril lines in build.prop that seems to have stabilized my data (Tested on MavROM on Straight Talk) these are ALREADY INCLUDED on the attached build.prop.
ro.ril.enable.3g.prefix=1
ro.ril.hep=0
ro.ril.hsxpa=5
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.hsupa.category=6
The main line here is "ro.ril.hep=0" all other lines are not required and may be placebo. This line seems to be key for making 3g stable, especially data roaming.
UPDATE
Updated the build.prop using the CM10 Kexec 11-03 as a base to bring it up to the 'latest' and reflect correct system version in system info.
Attached a reported patch to make the radio work on the XT860
Attached CM10.1 build.prop base CM10.1 2013-04-20
Attached CM10.2 build.prop base CM10.2 2013-08-14
REMEMBER TO RENAME THE FILE TO build.prop THEY ARE NOT ACTUAL ZIPS, THEY WILL FAIL TO UNZIP.
What version of radio is in your new link?
nemiroG1 said:
What version of radio is in your new link?
Click to expand...
Click to collapse
XT883 radio (Baseband n_34.18.16s)
Latest I can flash from XT883 files available
May or may not the right place to ask, but...
Do you guys know where I can find the correct patch for XT860 (if it exists)?
Thanks in advance.
Munckster said:
May or may not the right place to ask, but...
Do you guys know where I can find the correct patch for XT860 (if it exists)?
Thanks in advance.
Click to expand...
Click to collapse
It works for me
http://forum.xda-developers.com/showpost.php?p=33785558&postcount=3
migof said:
It works for me
http://forum.xda-developers.com/showpost.php?p=33785558&postcount=3
Click to expand...
Click to collapse
Thanks, mate.
I'll try it..
BTW - Does your phone gets really hot running JB?
how about ME863?
migof said:
It works for me
http://forum.xda-developers.com/showpost.php?p=33785558&postcount=3
Click to expand...
Click to collapse
Tried this ( XT860, Claro - Argentina , AOKP JB Kexec 03-11)
Phone and SMS work ( but I could get to this point already.
Still no Data ( 2g / 3g )
Thanks anyways
SeiferTV said:
Tried this ( XT860, Claro - Argentina , AOKP JB Kexec 03-11)
Phone and SMS work ( but I could get to this point already.
Still no Data ( 2g / 3g )
Thanks anyways
Click to expand...
Click to collapse
Same here. The data continuously turns on and off.
SeiferTV said:
Tried this ( XT860, Claro - Argentina , AOKP JB Kexec 03-11)
Phone and SMS work ( but I could get to this point already.
Still no Data ( 2g / 3g )
Thanks anyways
Click to expand...
Click to collapse
Same as you. Claro, XT860 and 03-11 AOKP. Installed the JB XT860 patch and now phone works, but i've got a com.android.phone FC when I try to go "Mobile networks" settings (to add APNs and stuff).
Its currently on GSM auto (PRL) as in stock rom (checked this in *#*#4636#*#*).
migof said:
It works for me
http://forum.xda-developers.com/showpost.php?p=33785558&postcount=3
Click to expand...
Click to collapse
Does data conectivity (3.5g / 3g) works with this patch?
As long as your provider has the frequencies for 3G the phone supports.
Must say that I flashed and followed steps and have mav rom 4.5 running on ST w./ att simple and works good. Using safestrap 3.05. Been trying to run cm10.1 3/10 build and a few other older builds of cm10.1 and have not been able to get modded build. Prop to work. Flashed g it in safestrap slot one in this order cm/gapps /build. Prop. It does not boot. If I do not include the modded build. Prop I get it to oot but of course no signal or baseband, phone number ect. Any suggestions? Really would like to fly 422 on this phone.
Sent from my XT883 using xda premium
amynjimmy said:
Must say that I flashed and followed steps and have mav rom 4.5 running on ST w./ att simple and works good. Using safestrap 3.05. Been trying to run cm10.1 3/10 build and a few other older builds of cm10.1 and have not been able to get modded build. Prop to work. Flashed g it in safestrap slot one in this order cm/gapps /build. Prop. It does not boot. If I do not include the modded build. Prop I get it to oot but of course no signal or baseband, phone number ect. Any suggestions? Really would like to fly 422 on this phone.
Sent from my XT883 using xda premium
Click to expand...
Click to collapse
Which build.prop are you trying to use? The one from the xt883 thread or the one I attached to the OP? The attached build.prop is not a flashable zip, remove the CM10.1.zip and put in /system and chmod 755. Tested on 3/06 and works for me, will be trying to update sometime soon to reflect newer system.
So open cm zip place in system(I know where it goes there) what is chmod 755
Sent from my XT883 using xda premium
amynjimmy said:
So open cm zip place in system(I know where it goes there) what is chmod 755
Sent from my XT883 using xda premium
Click to expand...
Click to collapse
Remove the zip extension, its not actually a zip. Chmod 755 is setting proper permissions. At the moment cm10.1 hashcode took out all the world phone stuff, so signal bars are broken, a bit complicated, etc. You can do it for fun, but I suggest to stick with mavrom (I use 4.0, 4.5 is exactly the same except it has overclock scripts, which have a bug and drain battery so I stuck with 4.0) also 4.2.2 still has the issue of not mounting the sd card (I just rebooted to 3/06 and neither internal nor external mounted) so definitely not a daily usage.
Ok so that would explain allot. I was running 4.5 and I can't get over 8hrs usage. Thanks for all the useful info.
Sent from my XT883 using xda premium
amynjimmy said:
Ok so that would explain allot. I was running 4.5 and I can't get over 8hrs usage. Thanks for all the useful info.
Sent from my XT883 using xda premium
Click to expand...
Click to collapse
Thanks for the thread. Needed a T-Mobile phone and this saved me some money. CDMA phones always seem to come cheaper around me.
Does anyone know how I'm getting 3G on T-Mobile though? I thought it only supported AT&T 3G bands.
gpgorbosjr said:
Thanks for the thread. Needed a T-Mobile phone and this saved me some money. CDMA phones always seem to come cheaper around me.
Does anyone know how I'm getting 3G on T-Mobile though? I thought it only supported AT&T 3G bands.
Click to expand...
Click to collapse
Tmobile is currently refarming its umts/hspa network to 1900MHz, which is the same as AT&T, and thus supported by the D3.
This website has user-reported sightings of refarmed areas. This of course is not all of them, feel free to report it yourself if you get 3g in your area and it's not shown.
Could someone mirror the build.props for the stock firmware and the cm10.2? The archives are corrupt when I try to open them.
EDIT: Never mind, it would help if I read though the entire post.
This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 4.x
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
-Call Forwarding
I'm constantly updating only this main thread and I will answer only in it, I have no time to update and control every thread in sub-forums.
I'm using this thread only for major notifications.
Mentor.37 said:
This is a patch to fully enable GSM on every rom and on every Android version.
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
The patch and the guide are available here.
If you want you can download a specific patch for the CyanogenMod 10.1.2 here.
Click to expand...
Click to collapse
it's worked on XT894 with Hashcode's CM10.1.2, i have tried it
such a nice work :good:
Does this enable the US GSM bands as well?
No, I'm sorry but it can't enable US GSM.
Awesome, added this to my GSM guide. Thank you.
Lum_UK said:
Awesome, added this to my GSM guide. Thank you.
Click to expand...
Click to collapse
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Mentor.37 said:
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Click to expand...
Click to collapse
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Lum_UK said:
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Click to expand...
Click to collapse
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Mentor.37 said:
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Click to expand...
Click to collapse
Can I use LTE (gsm networks sim) in my country with this patch (Be, Europe) ?
You have to se what are lte frequencies in Belgium.
The lte on xt894 only works at 700 mhz.
Maybe next time you should give credits to the original author... *cough cough*
Are you talking with me?
I'm the original author.
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
But they differ in a few lines, I think that tobby disabled the LTE. Anyway for nightlies is better to replace only the lines needed.
The world is full of people there is a chance that two of them to work on the same thing.
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Regards
Sent from my XT894 using xda app-developers app
lucize said:
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
Click to expand...
Click to collapse
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
lucize said:
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Click to expand...
Click to collapse
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
With copy, I was telling the way that you implemented the patch, and regarding to apn it was only a comment because in other cm releases(not motorola), the apn list is full (~180kb vs 17kb).
I personally downloaded the tobby zip first, but I use this device only recently (previous was d3) so who was the original poster I can't say.
Regards
Sent from my XT894 using xda app-developers app
I do not understand why you think I would have copied the way to implement the patch, patches are all made in the same way.
Personally I use my stock rom but several users who use AOSP roms have contacted me exposing the gsm problem and so I easily fixed with this patch using the settings that I use in my rom file build.prop.
At short will release a new version of my rom with a new build.prop file with new settings and I'll update this patch also.
I honestly did not know existed nor Tobby nor his zip, I created this patch because asked me.
Regarding the file APNs-conf.xml depends on the fact that the phone is born to the CDMA network Verizon and therefore not serving the other APNs, the file APNs-conf.xml in the stock rom is ~ 43KB.
What is the Tobby's zip?
Mentor.37 said:
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
Click to expand...
Click to collapse
Ah c'mon. Take a look into your own files. In apns-conf.xml is still my copyright... Its not extracted from Motorola Stock-ROM. Also not from CM. It's based on several sources on the internet (most of it is based on CM, but several more sources were added). It took days to combine the sources, remove duplicates, sort it, use the same style for every entry and so on. It's not a problem to use or copy this. But to say you did this yourself is not fair.
But apns-conf.xml is only one part of your mod. Second part is the automatic build.prop changer. (GSMbyMentor.sh)
Look at your GSMbyMentor.sh:
Code:
#!/sbin/sh
#
# Patch to enable GSM on Verizon by Mentor
# Build: 17.07.2013 17:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=GB/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.modem.mode =1/persist.ril.modem.mode =2/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.vzw.cdma.mdn=/persist.radio.vzw.cdma.mdn=deleted/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc = 1/ro.telephony.gsm-routes-us-smsc = 0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.ap.phonetype=2/persist.radio.ap.phonetype=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
Now let's take a look at the Bash-Script of "TobbysMod":
Code:
#!/sbin/sh
#
# Tobbys build.prop Anpassungen für das Droid 4
# Stand: 15.03.2013 04:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.language=en/ro.product.locale.language=de/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=DE/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.ecclist=911\,\*911\,\#911/persist.ril.ecclist=911\,\*911\,\#911\,119\,118\,999\,08\,000\,112\,110/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc=1/ro.telephony.gsm-routes-us-smsc=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.hwKeyboard.capsLockNoAlt=true/ro.hwKeyboard.capsLockNoAlt=false/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.lte.mm.disable=0/persist.radio.lte.mm.disable=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.lte_on_cdma=1/ro.mot.lte_on_cdma=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dateformat=MM-dd-yyyy/ro.com.android.dateformat=dd.mm.yyyy/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dataroaming=true/ro.com.android.dataroaming=false/g" /system/build.prop > /system/build.prop
Let's take a look at the differences.
- You removed my credit and changed the date
- you removed a few lines which were necessary for the keyboard-mod included in the original mod and necessary for European date-format and emergency calls
The rest stayed the same. Even the sequence/order. And you use exact the same trick for removing spaces. You can't say this was coincidence...
Third part of your mod is the edison install script. This looks different. Seems to be your own work.
Two of three parts in your mod copied from me. It's ok! I always wanted to remove the parts which are necessary for my German friends so everybody can use it, but I didn't have enough time. So it is good someone (you) did that. But please don't say it's your own work when you just copy files...
Link to original Thread for "TobbysMod": http://www.android-hilfe.de/motorol...82-tobbys-automatische-rom-modifizierung.html
Google translation: http://translate.google.de/translat...82-tobbys-automatische-rom-modifizierung.html
I added that apns-conf.xml at the suggestion of an user that tested my patch, I repeat that I'm on stock rom so I have not tested directly the patch. If you wont I can give you his email address.
In a first moment I made this patch as you can see here with the apns-conf.xml that I personally extracted and that I use in my rom for months without any problem. Anyway I removed that file.
About the sed is a common command for any linux user to manipulate text.
About the sequence/order it is different, I used the same in the build.prop.
About the point of the gsm patch, so the build.prop settings there are a lot of differences:
My:
Code:
telephony.lteOnCdmaDevice=0
persist.ril.modem.mode=2
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
persist.radio.vzw.cdma.mdn=deleted
ro.telephony.gsm-routes-us-smsc=0
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
Yours:
Code:
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
ro.mot.phonemode.vzw4gphone=0
persist.radio.lte.mm.disable=1
ro.mot.lte_on_cdma=0
These lines are missing in your:
Code:
persist.ril.modem.mode=2
persist.radio.vzw.cdma.mdn=deleted
persist.radio.ap.phonetype=1
and the lines that are equal in the two files have known each other forever and they are everywhere in the forums so what are you saying?
With the settings in my build.prop users solved their problem on aosp roms.
#Postedit
I found this and this with your patch and then this and this with my patch.
apns-conf.xml: As I said: You don't need to remove the file. It's ok I created this file to help users. Additionally because of the sources, I am not allowed to forbid the usage of this file for some users. You also don't NEED to give credits, because it's already included. I just wanted to mention you are not using your own file. Not more ore less.
Bash-Script: Yes, sed is a common linux command. But it's usage on the phone was a little bit different than on a normal linux machine and the trick with the spaces (sed -i "s/\ =/=/g") is not necessary for the function of this script. It's just to make some things a little bit easier. That's why it's hard to believe you found out the exact same thing as me and used it in exactly the same way. If you did: Grats mate! You must be a soulmate of me If you just used this because you saw it "somewhere" else: please don't remove my credit.
To the missing 3 lines: two of them are included in version 1.3 of 07/16/2013, one day before you created yours. Just "persist.radio.vzw.cdma.mdn=deleted" is not included in my Mod. I am just curious: What does this line do?
But we schouldn't argue about it. As I said: Feel free to use my work. I hope I am allowed to do the same with your work. Instead of argueing we should combine our work!
I reinserted the apns-conf.xml that I use in my rom.
I used the sed command intuitively how I use it.
The line "persist.radio.vzw.cdma.mdn=deleted" deactive the mdn on cdma network. I use these settings from time.
You can use my work without problem.
I just answered your allegations because I spent a lot of my free time for this my mod.
About a possible collaboration I like this idea, the work is much, time is short and one hand is always a pleasure.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
celoxhd
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Original dev supporter:
http://www.androidfilehost.com/?w=files&flid=12461
Click to expand...
Click to collapse
Huge thanks and credits to @titanic_fanatic
He ported the sources and provided all needed stuff to build it
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Phil3759 said:
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Click to expand...
Click to collapse
That's the correct path Maybe the driver isn't loading properly... I'll see if I can get a dmesg Log when booting recovery to see if the driver actually loads
Sent from my SGH-I757M using XDA Premium 4 mobile app
Vibrator Fixed
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
titanic_fanatic said:
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
Click to expand...
Click to collapse
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Phil3759 said:
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Click to expand...
Click to collapse
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
titanic_fanatic said:
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/...mmit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
Click to expand...
Click to collapse
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Phil3759 said:
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Click to expand...
Click to collapse
The first / is because it's part of a set of chained product copy files directives:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc \
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd \
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/lib/modules/vibrator.ko:recovery/root/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Click to expand...
Click to collapse
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
titanic_fanatic said:
The first / is because it's part of a set of chained product copy files directives:
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
Click to expand...
Click to collapse
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Phil3759 said:
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Click to expand...
Click to collapse
It seems that the extra \ was introduced in our JB branch and has never been fixed. Various examples in googles repo confirm that you are correct. I have removed the extra \ and added the properties you mentioned above to the cm.mk file. Here is the relevant commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
titanic_fanatic said:
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
Click to expand...
Click to collapse
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Phil3759 said:
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Click to expand...
Click to collapse
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
titanic_fanatic said:
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
Click to expand...
Click to collapse
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Phil3759 said:
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Click to expand...
Click to collapse
Can I get a link to these fixes please when you have it ready
titanic_fanatic said:
Can I get a link to these fixes please when you have it ready
Click to expand...
Click to collapse
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Phil3759 said:
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Click to expand...
Click to collapse
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
titanic_fanatic said:
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Phil3759 said:
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Click to expand...
Click to collapse
It is for the most part the same kernel with the few quirks of my device. More notably is my devices display drivers are mipi s6e8aa0_720hd and had to fork the kernel to apply some fixes to that driver as it's not maintained by cm.
Hmmm. I'll be the guinea pig. I will build with the new kernel and I'll test the recovery before you upload. I just think that the issue might be a memory leak in android causing the kernel to panic (overlay issue) and might not have an effect in recovery since its graphics are very basic.
I'll let you know when it's ready
Sent from my SGH-I757M using XDA Premium 4 mobile app