[ROM][ICS] Sawed Off Hand Edition - release 1 (CM9 - WiFi/BT) 20121020 + other ROMS

Search This thread
By:
Advanced…
A.VOID

A.VOID

Senior Member
Aug 10, 2010
1,093
68
Got to love disabling two major components of a smartphone in order for it not to fail.
My atrix began this crap a few weeks ago, and it has gotten progressively worse.
Trying to hold out until s3 is out, but its increasingly difficult.
My old captivate hqcad bad GPS hardware, wife's iPhone 4 has bad reception because
Of hardware, and now the atrix.

Where is the qc with these things?
 
Th3Bill

Th3Bill

Senior Member
Feb 6, 2012
6,307
9,280
Where I Am
A.VOID said:
Got to love disabling two major components of a smartphone in order for it not to fail.
My atrix began this crap a few weeks ago, and it has gotten progressively worse.
Trying to hold out until s3 is out, but its increasingly difficult.
My old captivate hqcad bad GPS hardware, wife's iPhone 4 has bad reception because
Of hardware, and now the atrix.

Where is the qc with these things?
Click to expand...
Click to collapse

Asleep at the wheel, my friend :)
 
ATRIXXIRTA

ATRIXXIRTA

Senior Member
Mar 17, 2012
2,434
768
The Shangri-La Motel
Notice how this ****e usually happens just over the 1 year mark. Just out of warranty coverage period..... conveniently enough.

At least it doesn't completely crap out after 3 months.... cough, cough, blackberry, cough:rolleyes:

Sent from my MB860 using XDA
 
C

Cusa

Senior Member
Dec 25, 2011
1,862
297
ATRIXXIRTA said:
Notice how this ****e usually happens just over the 1 year mark. Just out of warranty coverage period..... conveniently enough.

At least it doesn't completely crap out after 3 months.... cough, cough, blackberry, cough:rolleyes:

Sent from my MB860 using XDA
Click to expand...
Click to collapse

I have noticed this as well how just over the one year mark the phone starts ****ting on you. I have noticed that the digitizer is slowly going out on me and I don't think I can hold any longer for the damn SGS3.
 
crush

crush

Senior Member
Dec 22, 2010
1,466
24
Been using ATRIX for 6+ months, and I keep changing rims. Yet to see a single reboot. It might be few bad units which can happen to any manufacturer.

Sent from my MB860 using XDA
 
vagelisda

vagelisda

Senior Member
Feb 24, 2010
163
7
athens
First time I hear about this problem,and I certainly would not have a rom without wifi ! I would prefer to use a dumbphone instead,save my pocker some weight and volume also...

sent from my Atrix
 
D

djpablog

Member
May 3, 2007
12
1
This ROM worked great for me not a single reboot, my phone was basically unusable rebooting constantly to the point that i was just going to give up on it.. excellent work, thanks!
 
D

danstheman7

Senior Member
Apr 20, 2011
493
64
Long Island NY
mvniekerk said:
Howzit stalkers

There is a serious hardware flaw on our Atrix's (Atrices?) - the WiFi and Bluetooth module from Broadcom goes bust after a while - irrespective of which ROM you are using (even stock is not free from this problem).

You get random reboots, you only get "Error" when trying to connect to WiFi, and if you try again - it reboots. Same with Bluetooth.

That prompted me to make this build. It is CM9 with the WiFi and BT disabled. No more random reboots. This is a stop-gap measure until we can figure out what is causing this (most fingers point to the little battery on the CPU mainboard). This ROM just makes your phone usable again as a, you know, phone. HSPA also works. You can reverse tether with a USB cable to use your PC's internet - if you are interested and you are using Ubuntu I can give you an app I made for this purpose.

Please, keep the discussion on this forum on the topic of FINDING OUT WHAT IS CAUSING THIS.
There is a plethora of other forums with other users also experiencing this problem - no "me too" nonsense, please. It is a recognized problem. The pet protection agency will be forced to euthenize a little fluffy baby kitten if you post a "me too" post.

WHAT IS DISABLED
WiFi
Bluetooth

What doesn't work
Camera (will try to fix this in the next release)
Video Camera
Fingerprint sensor (usual CM9)
Webtop (usual CM9)

Link
http://depositfiles.com/files/o9jyr61a2
http://ifolder.ru/30516689
Click to expand...
Click to collapse

I made a thread accidentally before seeing your post, located here.
http://xdaforums.com/showthread.php?p=26426770

If you'd like to host your ROM on my server instead of those mirrors, feel free to PM me :)

Otherwise, thanks, will try this rom once it's done downloading (1hr+ :( )
 
neer2005

neer2005

Senior Member
Feb 20, 2011
754
121
New Jersey
My ATRIX also crapped out on me. No wifi :( , can't we get enough exposure to make Motorola do something about it?

Sent from my MB860 using XDA
 
D

danstheman7

Senior Member
Apr 20, 2011
493
64
Long Island NY
Also...I have no sound on phone calls, on top of the no wifi/BT. Am I the only one with this symptom?

**edit**
internal speaker of phone is apparently connected to the phone earpiece, which in my phone, is partially broken.
not related to wifi/bt/rebooting issue.
 
Last edited:
jakis39

jakis39

Senior Member
Nov 16, 2010
381
104
Seriously, is this supposed to be "Sawned" or "Sawed" ? This has been bothering me for a full week now and I can't believe no one else has commented on it. Am I missing something here?
 
D

danstheman7

Senior Member
Apr 20, 2011
493
64
Long Island NY
Potential Solution

Alright, update.

I took apart my phone, and removed, then re-soldered the small battery within the device (only because I accidentally ripped it off the PCB. All you really need to do is lift it up off the contact point, then push it back onto the contact point [as shown in the video])

It TEMPORARILY fixed the wifi-and only temporarily. It lasted three minutes or so, then turned off, and the phone started rebooting again.

Not sure if the battery needs to be replaced or what, but it definitely has something to do with why our WiFi no longer works.

Followed this video:
http://www.youtube.com/watch?v=SYz_RiuFVRk

Used IFixIt to figure out which screws needed to be replaced.

Unfortunately I had to drill through the screws (only the silver ones around the outside, not the black screws) to remove the back, because I had no T5 Torx screwdriver, and I stripped the original screws that came with the phone.

MAKE SURE, if you're going to attempt to remove the back, THAT YOU BUY A T5 TORX (or the correct specific size, don't quote me on the fact it's size T5).

Good luck.

Oh, and also, the no sound during calls is related to my hardware. After playing with the speaker, I realized they're both linked.
I've ordered a replacement backing (which includes antenna, speaker, aux jack).
 
  • Like
Reactions: mvniekerk
r1c47

r1c47

Senior Member
Jul 17, 2011
103
11
neer2005 said:
My ATRIX also crapped out on me. No wifi :( , can't we get enough exposure to make Motorola do something about it?
Click to expand...
Click to collapse

Media exposure, like, get "big" media sites to post about it on their front page, like xda, engadget, ars, etc. and hopefully get a recall.
Out something like that.
 
nerfman100

nerfman100

Senior Member
Jan 11, 2012
401
93
r1c47 said:
Media exposure, like, get "big" media sites to post about it on their front page, like xda, engadget, ars, etc. and hopefully get a recall.
Out something like that.
Click to expand...
Click to collapse

A recall? I'm sure it's too late for that. ;) Plus, if there was a recall, they'd probably give us ones without BL-unlocking. :(
 
M

mvniekerk

Senior Member
Feb 11, 2010
127
384
Johannesburg
danstheman7 said:
It TEMPORARILY fixed the wifi-and only temporarily. It lasted three minutes or so, then turned off, and the phone started rebooting again.

Not sure if the battery needs to be replaced or what, but it definitely has something to do with why our WiFi no longer works.
Click to expand...
Click to collapse

Thanks DansTheMan. My feeling exactly - I also did the remove-battery-from-contact thing and it also temporarily fixed the issue for me. Just shortly after 5 minutes it start kicking my dog again.

As to really making sure that the battery is the problem, one should find out the voltage of that battery, get a bench power supply, short out the battery and supply the voltage (through the bps), put on the phone and see if the problem still persists.

As to Sawned vs Sawed off - correct English is Sawed. I'm claiming English as second language as my defence :)
 
You must log in or register to reply here.

Similar threads

jokersax11
[ROM] unofficial CM9 by jokersax 7/04/2012
Replies
10K
Views
3M
P
palmbeach05
epinter
[ROM] CM10 (JellyBean) for Atrix
Replies
6K
Views
2M
D
DuyguSeli
T
[ROM] Atrix CM9 [ADT's SelfKANGish builds - 20120715]
Replies
2K
Views
818K
W
williamfrench
epinter
[ROM] CM 10.1(Android 4.2) for Atrix
Replies
4K
Views
1M
W
williamfrench
Notorious544d
[CM7] Neutrino ROM V2.9 ¦ V3.00b1 [24/02]
Replies
10K
Views
2M
J
jman316

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 7
    M
    mvniekerk
    UPDATE
    http://xdaforums.com/showthread.php?p=33043197#post33043197
    An app removing WiFi/BT from your Atrix, stopping the reboots. El Noob friendly.
    Click to expand...
    Click to collapse
    Howzit stalkers

    There is a serious hardware flaw on our Atrix's (Atrices?) - the WiFi and Bluetooth module from Broadcom goes bust after a while - irrespective of which ROM you are using (even stock is not free from this problem).

    You get random reboots, you only get "Error" when trying to connect to WiFi, and if you try again - it reboots. Same with Bluetooth.

    That prompted me to make this build. It is CM9 with the WiFi and BT disabled. No more random reboots. This is a stop-gap measure until we can figure out what is causing this (most fingers point to the little battery on the CPU mainboard). This ROM just makes your phone usable again as a, you know, phone. HSPA also works. You can reverse tether with a USB cable to use your PC's internet - if you are interested and you are using Ubuntu I can give you an app I made for this purpose.

    Please, keep the discussion on this forum on the topic of FINDING OUT WHAT IS CAUSING THIS.
    There is a plethora of other forums with other users also experiencing this problem - no "me too" nonsense, please. It is a recognized problem. The pet protection agency will be forced to euthenize a little fluffy baby kitten if you post a "me too" post.
    UPDATE - How to make it work in other ROMS
    Some adb shell commands - you should be able to use / know what adb is (I'm no good at clockwork zip scripts - yet - so this will do):
    adb shell
    su bash
    mount
    //Then, look for something like "/dev/block/mmcblk0p12 /system ext4" - key is the /system part
    mount -o rw,remount /dev/block/mmcblk0p12 /system/
    cd /system/lib/modules
    mv dhd.ko dhd.ko2

    That's it - confirmed to work with Jokersax's 0.6 release and Turl's. Will probably work on older systems as well, seeming that all use the same archaic Froyo f-ing kernel.
    Click to expand...
    Click to collapse

    WHAT IS DISABLED
    WiFi
    Bluetooth

    What doesn't work
    Camera (will try to fix this in the next release)
    Video Camera
    Fingerprint sensor (usual CM9)
    Webtop (usual CM9)

    Link
    http://depositfiles.com/files/o9jyr61a2
    http://ifolder.ru/30516689
    View
    6
    jokersax11
    jokersax11
    So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.

    Sent from my MB855 using XDA
    View
    2
    M
    mvniekerk
    [ 31.028143] sdhci_tegra_wlan_detect Detecting WLAN
    [ 31.028164] mot_wifi_set_carddetect: Nobody to notify
    [ 31.029391]
    [ 31.029395] Dongle Host Driver, version 4.218.248.32
    [ 31.029400] Compiled in /tank/jokersax/cm9/kernel/moto/olympus/wifi-module/wlan/osrc/open-src/src/dhd/linux/../.. on May 7 2012 at 11:40:09
    [ 31.328158] mmc1: error -110 whilst initialising SDIO card

    WARNING: at /tank/jokersax/cm9/kernel/moto/olympus/lib/kobject.c:595 kobject_put+0x50/0x60()
    [ 214.627572] kobject: '<NULL>' (0003da74): is not initialized, yet kobject_put() is being called.
    [ 214.627581] Modules linked in: dhd(+)
    [ 214.627591] Backtrace:
    [ 214.627612] [<c0040010>] (dump_backtrace+0x0/0x10c) from [<c05b68c8>] (dump_stack+0x18/0x1c)
    [ 214.627622] r7:c031c6c4 r6:c071fb48 r5:00000253 r4:e83a1e98
    [ 214.627647] [<c05b68b0>] (dump_stack+0x0/0x1c) from [<c00bc5b8>] (warn_slowpath_common+0x50/0x68)
    [ 214.627663] [<c00bc568>] (warn_slowpath_common+0x0/0x68) from [<c00bc61c>] (warn_slowpath_fmt+0x30/0x38)
    [ 214.627673] r7:bf081000 r6:00000000 r5:bf076570 r4:0003da74
    [ 214.627692] [<c00bc5ec>] (warn_slowpath_fmt+0x0/0x38) from [<c031c6c4>] (kobject_put+0x50/0x60)
    [ 214.627701] r3:00000000 r2:c071fb80
    [ 214.627720] [<c031c674>] (kobject_put+0x0/0x60) from [<c03787f0>] (put_driver+0x14/0x18)
    [ 214.627729] r4:e98390c0
    [ 214.627742] [<c03787dc>] (put_driver+0x0/0x18) from [<c0378938>] (driver_register+0x144/0x164)
    [ 214.627757] [<c03787f4>] (driver_register+0x0/0x164) from [<c037994c>] (platform_driver_register+0x4c/0x60)
    [ 214.627767] r9:00000000 r8:00000000 r7:bf081000 r6:00000000 r5:e83a0000
    [ 214.627782] r4:bf078890
    [ 214.627826] [<c0379900>] (platform_driver_register+0x0/0x60) from [<bf049fa4>] (wifi_add_dev+0x24/0x40 [dhd])
    [ 214.627870] [<bf049f80>] (wifi_add_dev+0x0/0x40 [dhd]) from [<bf0810bc>] (init_module+0xbc/0x238 [dhd])
    [ 214.627902] [<bf081000>] (init_module+0x0/0x238 [dhd]) from [<c003b5c8>] (do_one_initcall+0x40/0x1bc)
    [ 214.627912] r5:e83a0000 r4:c07e0c00
    [ 214.627932] [<c003b588>] (do_one_initcall+0x0/0x1bc) from [<c00f3880>] (sys_init_module+0xcc/0x200)
    [ 214.627941] r9:e83a0000 r8:c003c364 r7:00046bd8 r6:00000000 r5:bf076748
    [ 214.627957] r4:5c126008
    [ 214.627970] [<c00f37b4>] (sys_init_module+0x0/0x200) from <c003c1e0>] (ret_fast_syscall+0x0/0x2c)
    [ 214.627979] r7:00000080 r6:5e0fdb34 r5:5c126008 r4:405ad0f0
    [ 214.627995] ---[ end trace 2416c978061dd5a5 ]---
    [ 214.628002] Error: Driver 'bcm4329_wlan' is already registered, aborting...

    Now I had some experience with WiFi kernel driver development (iMx51 + CSR based WiFi/BT combo chip).
    The startup sequence on kernel level will probably go like this:
    1) Kernel startup
    2) ARM CPU specifics startup
    3) Platform specific device setup (setup clocks)
    3) Platform driver dependency registration (like, on SDIO 1 there is a WiFI chip that needs driver X to work)
    4) Sub-platform driver startup (SPI, SDIO, UART, I2C)
    I think this is where we fail first - Error -110 means timeout. Each MMC / SDIO chip has a MMC specific startup sequence, then depending what was given on number 3, it jumps over to SDIO (SDIO is a superset of MMC).
    When our BT/WiFi chip is put into SDIO mode, the SDIO commands fail with a time out.

    Possible reasons for it failing:
    1) Incorrect voltages
    2) Skewed clock
    3) Busted chip.
    4) We talk to it too fast
    5) Kernel is messed up

    Now, seeing that (through weird loops, check my previous post) I could get the unit running two more times, I do not think it is 3.

    Why it could be 1:
    Voltage rails needs to start up at the correct sequence for some chips. Like some chips will specify an operating range of between 1.8V and 3.3V. That means if it finds 5V on it, it will shut itself off. Sometimes some chips needs an initial 3V, then after 10 seconds it can be put into 1.8V (in-chip startup). Sometimes, it needs 10seconds to stabilize before you can talk to it (in our case via SDIO).
    Why it isn't 1:
    I've tried a lot of other kernels. It is all based of the ATT code, and they do the voltage rail setup correctly. I've even reverted back to stock code - no dice.

    Why it could be 2
    By removing the small cell battery, the drain on the battery was lifted. It could then store up enough current to put itself into the correct clock rate when it was put back.
    Why it isn't 2
    ? Don't know. More needs to be known of the function of this battery. Obviously it is driving some RTC (real time clock). RTC's normally work at 32MHz, (32768, easilly divideable by 2, 4, 8 etc).
    Does the Broadcom chip need this RTC? Isn't its clock lines driven by the Tegra2?

    Why it could be 4
    If the RTC is compromised (number 2) then init will suffer. If the Tegra's clock is not derived from the battery and the Broadcom's is, then there will be a disparity between the 2 units chatting together, as SDIO communication is clock based and not latch based (like SPI). If I'm chatting to you at 32MHz and you are 5% off, then we will not be communicating (if you are an SDIO master and I'm an SDIO slave).
    Why it isn't
    No idea.

    Why it could be 5
    Bunch of kernel errors stating un-inited modules pointing to null.

    Why it isn't 5
    Stock kernels also have the same problem

    So, sorry folks, this issue points to a hardware problem.
    Our biggest answer will be at the following:
    1) What does that battery do?
    2) Why is the SDIO subsystem having timeouts?
    View
    2
    M
    moleg
    mirror1
    View
    1
    M
    mvniekerk
    jokersax11 said:
    So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.

    Sent from my MB855 using XDA
    Click to expand...
    Click to collapse

    No, I've changed the kernel. On arch/arm/mach-tegra/ I've changed board-mot.c to not do wifi init and also removed board-mot-wlan.c from the Makefile. This keeps the SDIO card from being init-ed and is sufficient for the driver not to be registered.

    Yes, having an update that is more frugal than having a 125MB update will probably work. But I don't have the inclination to do that now, as making my own custom kernel + ensuring it working with turl's base + a custom update script is not in the depth I want to waddle in now. Unless someone wants to help me with it. It is really a 2 line patch stretching on these 2 files.

    As from "just switching off wifi and bluetooth" - there are SDIO interrupts being enabled from the GPIO and (subsequently) on the SDIO card (the Broadcom 4329). That means, even if you disable these 2, IRQ interrupts will still happen = the phone will still reboot.
    View

New posts