[ROM][Official]MyTouch4G Slide CyanogenMod 9 Alpha 6 (07/23) - 4.0.4

Search This thread
By:
Advanced…
T

txmtb

Member
Jan 13, 2012
43
9
dansl said:
OK.. so... wiped everything + flashed CM9 Alpha 5 + entered SIM unlock code, still no dice... when i go to "Network Operators" it says "Error while searching for networks", and there is nothing in APNs settings...

Same issue on Virtuous Inquisition... Going to try a stock ROM.



So, after you flashed MikTouch, you flash CM9 and it still works with AT&T SIM?
Click to expand...
Click to collapse

Yep. I had CM9 on there and was changing to AT&T. But it wouldn't take my unlock code like you said. I saw that MikTouch was "stock based" so I flashed it. Put in the AT&T SIM, entered the unlock code. Checked to make sure it was working, and then flashed back to CM9, Alpha 3 I think, and it has worked since then. I did complete wipes between flashing the ROM's back and forth. BTW, mine is working fine but I still get the "Error searching for networks" on mine if I do a manual search. I just have it set to "Select automatically" and haven't had any issues.
 
Last edited:
hapa8o8

hapa8o8

Senior Member
Aug 14, 2010
266
43
Honolulu, Hawaii
E/CameraHolder( 7388): fail to connect Camera

So, Here is my Logcat again, after this issue occurred...
This has been a persistent issue with CM9 Alpha for me.:crying: I am an avid user of our Doubleshot's Camera (since it is epically uber~!) :highfive:

Any others have an issue with this?
Anyone have a suggestion for a fix? :D

AND WTF is this org.apache.http.impl.conn...??? :confused:

Code: 
Log Collector version: 1.1.0
Device model: myTouch_4G_Slide
Firmware version: 4.0.4
Kernel version: 3.0.30-CyanogenMod-g362b2f8
jparker@slickback )
#1 SMP PREEMPT Tue Jun 26 14:53:26 CDT 2012
Build number: cm_doubleshot-userdebug 4.0.4 IMM76L eng.jparker.20120626.144234 test-keys

--------- beginning of /dev/log/system
06-29 12:32:34.435 I/ActivityManager(  218): No longer want com.android.voicedialer (pid 3482): hidden #16
--------- beginning of /dev/log/main
06-29 12:32:34.665 I/mm-camera(  131): ...config thread select timeout...
06-29 12:32:34.885 I/MobclickAgent( 7409): IOException,Failed to send message.
06-29 12:32:34.885 I/MobclickAgent( 7409): org.apache.http.conn.HttpHostConnectException: Connection to http://www.umeng.co refused
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
06-29 12:32:34.885 I/MobclickAgent( 7409): at com.mobclick.android.MobclickAgent.a(Unknown Source)
06-29 12:32:34.885 I/MobclickAgent( 7409): at com.mobclick.android.MobclickAgent.c(Unknown Source)
06-29 12:32:34.885 I/MobclickAgent( 7409): at com.mobclick.android.MobclickAgent.c(Unknown Source)
06-29 12:32:34.885 I/MobclickAgent( 7409): at com.mobclick.android.b.run(Unknown Source)
06-29 12:32:34.885 I/MobclickAgent( 7409): at android.os.Handler.handleCallback(Handler.java:605)
06-29 12:32:34.885 I/MobclickAgent( 7409): at android.os.Handler.dispatchMessage(Handler.java:92)
06-29 12:32:34.885 I/MobclickAgent( 7409): at android.os.Looper.loop(Looper.java:137)
06-29 12:32:34.885 I/MobclickAgent( 7409): at android.os.HandlerThread.run(HandlerThread.java:60)
06-29 12:32:34.885 I/MobclickAgent( 7409): Caused by: java.net.ConnectException: failed to connect to /211.151.139.246 (port 80) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
06-29 12:32:34.885 I/MobclickAgent( 7409): at libcore.io.IoBridge.isConnected(IoBridge.java:214)
06-29 12:32:34.885 I/MobclickAgent( 7409): at libcore.io.IoBridge.connectErrno(IoBridge.java:152)
06-29 12:32:34.885 I/MobclickAgent( 7409): at libcore.io.IoBridge.connect(IoBridge.java:112)
06-29 12:32:34.885 I/MobclickAgent( 7409): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
06-29 12:32:34.885 I/MobclickAgent( 7409): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
06-29 12:32:34.885 I/MobclickAgent( 7409): at java.net.Socket.connect(Socket.java:842)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
06-29 12:32:34.885 I/MobclickAgent( 7409): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:144)
06-29 12:32:34.885 I/MobclickAgent( 7409): ... 14 more
06-29 12:32:34.885 I/MobclickAgent( 7409): Caused by: libcore.io.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
06-29 12:32:34.885 I/MobclickAgent( 7409): at libcore.io.IoBridge.isConnected(IoBridge.java:201)
06-29 12:32:34.885 I/MobclickAgent( 7409): ... 21 more
06-29 12:32:34.885 W/System.err( 7409): org.apache.http.conn.HttpHostConnectException: Connection to http://www.umeng.co refused
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:183)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
06-29 12:32:34.885 W/System.err( 7409): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
06-29 12:32:34.885 W/System.err( 7409): at com.mobclick.android.MobclickAgent.a(Unknown Source)
06-29 12:32:34.885 W/System.err( 7409): at com.mobclick.android.MobclickAgent.c(Unknown Source)
06-29 12:32:34.885 W/System.err( 7409): at com.mobclick.android.MobclickAgent.c(Unknown Source)
06-29 12:32:34.885 W/System.err( 7409): at com.mobclick.android.b.run(Unknown Source)
06-29 12:32:34.895 W/System.err( 7409): at android.os.Handler.handleCallback(Handler.java:605)
06-29 12:32:34.895 W/System.err( 7409): at android.os.Handler.dispatchMessage(Handler.java:92)
06-29 12:32:34.895 W/System.err( 7409): at android.os.Looper.loop(Looper.java:137)
06-29 12:32:34.895 W/System.err( 7409): at android.os.HandlerThread.run(HandlerThread.java:60)
06-29 12:32:34.895 W/System.err( 7409): Caused by: java.net.ConnectException: failed to connect to /211.151.139.246 (port 80) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
06-29 12:32:34.895 W/System.err( 7409): at libcore.io.IoBridge.isConnected(IoBridge.java:214)
06-29 12:32:34.895 W/System.err( 7409): at libcore.io.IoBridge.connectErrno(IoBridge.java:152)
06-29 12:32:34.895 W/System.err( 7409): at libcore.io.IoBridge.connect(IoBridge.java:112)
06-29 12:32:34.895 W/System.err( 7409): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
06-29 12:32:34.895 W/System.err( 7409): at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
06-29 12:32:34.895 W/System.err( 7409): at java.net.Socket.connect(Socket.java:842)
06-29 12:32:34.895 W/System.err( 7409): at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
06-29 12:32:34.895 W/System.err( 7409): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:144)
06-29 12:32:34.895 W/System.err( 7409): ... 14 more
06-29 12:32:34.895 W/System.err( 7409): Caused by: libcore.io.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
06-29 12:32:34.895 W/System.err( 7409): at libcore.io.IoBridge.isConnected(IoBridge.java:201)
06-29 12:32:34.895 W/System.err( 7409): ... 21 more
06-29 12:32:34.895 I/MobclickAgent( 7409): send applog failed
06-29 12:32:35.916 I/ActivityManager(  218): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera bnds=[33,510][144,633]} from pid 466
06-29 12:32:36.036 D/OpenGLRenderer(  466): Flushing caches (mode 1)
06-29 12:32:36.066 V/CameraHolder( 7388): open camera 0
06-29 12:32:36.066 W/CameraService(  131): CameraService::connect X (pid 7388) rejected (existing client).
06-29 12:32:36.066 E/CameraHolder( 7388): fail to connect Camera
06-29 12:32:36.066 E/CameraHolder( 7388): java.lang.RuntimeException: Fail to connect to camera service
06-29 12:32:36.066 E/CameraHolder( 7388): at android.hardware.Camera.native_setup(Native Method)
06-29 12:32:36.066 E/CameraHolder( 7388): at android.hardware.Camera.<init>(Camera.java:320)
06-29 12:32:36.066 E/CameraHolder( 7388): at android.hardware.Camera.open(Camera.java:280)
06-29 12:32:36.066 E/CameraHolder( 7388): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
06-29 12:32:36.066 E/CameraHolder( 7388): at com.android.camera.Util.openCamera(Util.java:292)
06-29 12:32:36.066 E/CameraHolder( 7388): at com.android.camera.Camera$4.run(Camera.java:1167)
06-29 12:32:36.066 E/CameraHolder( 7388): at java.lang.Thread.run(Thread.java:856)
06-29 12:32:36.106 D/dalvikvm(  218): GC_CONCURRENT freed 1630K, 45% free 8011K/14531K, paused 6ms+6ms
06-29 12:32:36.116 D/OpenGLRenderer(  466): Flushing caches (mode 0)
06-29 12:32:36.347 D/dalvikvm(  218): GC_EXPLICIT freed 60K, 46% free 7959K/14531K, paused 2ms+5ms
06-29 12:32:36.377 V/camera  ( 7388): surfaceChanged. w=480. h=640
06-29 12:32:36.427 I/ActivityManager(  218): Displayed com.android.camera/.Camera: +438ms
06-29 12:32:37.468 D/dalvikvm(  466): GC_FOR_ALLOC freed 313K, 32% free 9557K/14019K, paused 28ms
06-29 12:32:37.568 D/dalvikvm(  466): GC_FOR_ALLOC freed 9K, 30% free 9917K/14019K, paused 76ms
06-29 12:32:37.618 D/dalvikvm(  466): GC_FOR_ALLOC freed 5K, 29% free 10261K/14403K, paused 29ms
06-29 12:32:37.668 D/dalvikvm(  466): GC_FOR_ALLOC freed 5K, 29% free 10606K/14787K, paused 41ms
06-29 12:32:37.708 D/dalvikvm(  466): GC_FOR_ALLOC freed <1K, 28% free 10945K/15171K, paused 29ms
06-29 12:32:38.259 W/InputManagerService(  218): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41307e10
06-29 12:32:38.299 D/dalvikvm(  466): GC_FOR_ALLOC freed 26K, 28% free 11311K/15555K, paused 32ms
06-29 12:32:38.349 D/OpenGLRenderer( 7388): Flushing caches (mode 0)
06-29 12:32:38.379 D/dalvikvm(  466): GC_FOR_ALLOC freed 1763K, 36% free 10579K/16323K, paused 41ms
06-29 12:32:38.469 D/dalvikvm(  466): GC_FOR_ALLOC freed 26K, 25% free 12311K/16323K, paused 27ms
06-29 12:32:38.539 D/dalvikvm(  466): GC_FOR_ALLOC freed 6K, 24% free 13339K/17475K, paused 30ms
06-29 12:32:38.619 D/dalvikvm(  466): GC_FOR_ALLOC freed 2K, 23% free 14697K/19011K, paused 30ms
06-29 12:32:38.689 D/dalvikvm(  466): GC_FOR_ALLOC freed 4438K, 42% free 11972K/20547K, paused 29ms
06-29 12:32:38.789 D/dalvikvm( 1417): GC_CONCURRENT freed 5692K, 64% free 4516K/12288K, paused 3ms+3ms
06-29 12:32:38.829 W/CursorWrapperInner( 1417): Cursor finalized without prior close()
06-29 12:32:38.829 W/CursorWrapperInner( 1417): Cursor finalized without prior close()
06-29 12:32:38.859 I/ActivityManager(  218): No longer want com.google.android.gallery3d (pid 3538): hidden #16
06-29 12:32:38.889 D/OpenGLRenderer( 7388): Flushing caches (mode 1)
06-29 12:32:38.949 D/dalvikvm( 7388): GC_EXPLICIT freed 1225K, 73% free 3397K/12288K, paused 3ms+5ms
06-29 12:32:39.460 I/ActivityManager(  218): START {act=com.anddoes.launcher.ACTION flg=0x10000000 cmp=com.anddoes.launcher/.Launcher bnds=[192,707][288,800] (has extras)} from pid 466
06-29 12:32:40.671 I/mm-camera(  131): ...config thread select timeout...
06-29 12:32:43.744 I/ActivityManager(  218): No longer want com.android.vending (pid 1611): hidden #16
06-29 12:32:46.667 I/mm-camera(  131): ...config thread select timeout...
06-29 12:32:49.780 I/ActivityManager(  218): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.anddoes.launcher/.Launcher} from pid 218
06-29 12:32:52.683 I/mm-camera(  131): ...config thread select timeout...
06-29 12:32:52.693 I/ActivityManager(  218): START {act=com.anddoes.launcher.ACTION flg=0x10000000 cmp=com.anddoes.launcher/.Launcher bnds=[192,707][288,800] (has extras)} from pid 466
06-29 12:32:53.063 I/dalvikvm(  466): Jit: resizing JitTable from 4096 to 8192
06-29 12:32:58.438 D/BATT_PYD(  135): Pyramid_calculate_level: Get percent_last:72
06-29 12:32:58.438 I/BATT_ALG(  135): vol=3681;curr=0;dis_curr=723;temp=118;id=3;level=71;chg_src=0;chg_en=0;ov_chg=0;temp_range=0;timer=60;safety_count=0
06-29 12:32:58.679 I/mm-camera(  131): ...config thread select timeout...
06-29 12:33:04.694 I/mm-camera(  131): ...config thread select timeout...
06-29 12:33:07.687 I/ActivityManager(  218): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.xtralogic.android.logcollector/.SendLogActivity} from pid 466
06-29 12:33:07.757 I/ActivityManager(  218): Start proc com.xtralogic.android.logcollector for activity com.xtralogic.android.logcollector/.SendLogActivity: pid=7631 uid=10102 gids={1007, 1015}
06-29 12:33:07.827 I/dalvikvm( 7631): Turning on JNI app bug workarounds for target SDK version 3...
06-29 12:33:07.928 V/PhoneStatusBar(  329): setLightsOn(true)
06-29 12:33:08.028 I/ActivityManager(  218): Displayed com.xtralogic.android.logcollector/.SendLogActivity: +285ms
06-29 12:33:09.689 I/ActivityManager(  218): No longer want com.keramidas.TitaniumBackup (pid 1666): hidden #16
06-29 12:33:09.699 W/InputManagerService(  218): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@415c4118
06-29 12:33:10.700 I/mm-camera(  131): ...config thread select timeout...
06-29 12:33:13.203 I/ActivityManager(  218): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.xtralogic.android.logcollector/.SendLogActivity bnds=[96,211][192,361]} from pid 466
06-29 12:33:13.333 V/PhoneStatusBar(  329): setLightsOn(true)
06-29 12:33:13.433 I/ActivityManager(  218): Displayed com.xtralogic.android.logcollector/.SendLogActivity: +173ms
 
dillalade

dillalade

Senior Member
Sep 28, 2009
1,543
366
Richmond
@ teamDS

Do you guys think you will get a chance to work on the TVout feature. It's awesome we have it functioning to some degree ;)

It would be amazing if TVout can work as well as on stock rom. The lag/refresh cycle in the current TVout app is not really usable for gaming I find. And videos - youtube atleast doesn't render on the TV at all for me.

Hope you can work some magic on this.
Tbh this is one of the only key features I think we need to refine, because everything else runs so well.

:thumbup:

Sent from my myTouch_4G_Slide using xda app-developers app
 
  • Like
Reactions: Lockdo6307, cj chitwood and AgentCherryColla
seansc144

seansc144

Senior Member
Jul 6, 2008
1,185
350
Brooklyn
Will anyone bring jellybean to the 4gmytouch slide..I would like to See a cm9 jellybean rom
Sent from my myTouch_4G_Slide using XDA
 
Last edited:
Coug76

Coug76

Senior Member
Feb 27, 2011
2,267
976
East of Seattle
seansc144 said:
Will anyone bring jellybean to the 4gmytouch slide
Sent from my myTouch_4G_Slide using XDA
Click to expand...
Click to collapse

Virtuous had a port from the SDK for the Gnex already. That is super fast. I'm sure that work will start sooner or later. Once the Sensation community starts work it is only a matter of time before we get it.

CM9 rocks (too keep it on topic).

Hastily spouted for your befuddlement
 
  • Like
Reactions: seansc144
cj chitwood

cj chitwood

Senior Member
Jun 7, 2009
612
79
Cowford, FL - OnePlus 7T running Res Remix 8.5.9
plus.google.com
Coug76 said:
I'm sure that work will start sooner or later. Once the Sensation community starts work it is only a matter of time before we get it.
Click to expand...
Click to collapse


Add to that the fact that we now have a few ways to unlock the bootloader, at least two ways to off the S-, and now at least two mainstream devs who have the doubleshot (at least one of whom does not use it for a primary device, making it less risky to do risky experimental stuff with it)... plus, after reportedly EOLing the device about a year ago, T-Mobile is also reportedly still selling it at or near its original price (indicating the demand is strong enough to support such pricing)(of course I read that somewhere but haven't checked for myself). I am confident that this device will see jellybean and maybe even whatever the K-android will be (especially if we can all support the devs in some way).

--
Sent from my HTC Swiss Army Doubleshot running, at least for the moment, CM9a5
 
AgentCherryColla

AgentCherryColla

Senior Member
Jan 15, 2012
1,472
510
Carpentersville
seansc144 said:
Will anyone bring jellybean to the 4gmytouch slide
Sent from my myTouch_4G_Slide using XDA
Click to expand...
Click to collapse

I started a bounty thread in Gen. Everybody knows money helps development. Once the source is available, XMC is going to build Jellybean. I'm sure Tbalden will give us a taste of Jellybean once CM9 is RC. Our device is more than capable of running it.

Sent from my myTouch_4G_Slide using Tapatalk 2
 
  • Like
Reactions: seansc144
I

infernodemon2005

Senior Member
Dec 25, 2011
56
3
Don't get me wrong... I love the taste of this icecream sandwitch... but that jellybean also looks good lol. If google would quit with the sweet treat names these kinds of jokes wouldn't be so easy. Anyway, still loving cm9 and looking forward to seeing the full rc. Will be rocking it till we taste the jellybean lol

Sent from my myTouch_4G_Slide using Tapatalk 2
 
  • Like
Reactions: seansc144
dillalade

dillalade

Senior Member
Sep 28, 2009
1,543
366
Richmond
strapped365 said:
My Evo Shift only uses 3% every 15 hours of sleep

Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse

You were saying....

Screenshot_2012-07-01-10-59-49.png


I just woke up & to my pleasant surprise I saw this (I might add, wifi & sync were on too.). :D

This is currently illustrating my third cycle of CM9-A5.
Both previous gave me over a day up time.
This 3rd cycle could be epic :thumbup:

Sent from my myTouch_4G_Slide using xda app-developers app
 
Last edited:
strapped365

strapped365

Senior Member
Mar 14, 2011
5,159
2,795
Columbus
dillalade said:
Kotedia

You were saying....

Screenshot_2012-07-01-10-59-49.png


I just woke up & to my pleasant surprise I saw this (I might add, wifi & sync were on too.). :D

This is currently illustrating my third cycle of CM9-A5.
Both previous gave me over a day up time.
This 3rd cycle could be epic :thumbup:

Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse

Yeah that's what mine should have looked like, but if you find my screen shot, you will see 20% battery loss, and virtually no usage......that was using my anker 1900. Battery has gotten better but no where near yours. Also if you see my screenie I was on wifi the whole time as well.

*edit*
Kotedia?


ae652db7-51a0-3503.jpg


This here is actually good usage, for some reason the big jump was when I hit recovery and did a nand back to cm9. I was on MikTouch so I could have the camera for my little ones birthday, as soon as it was over I did a nand and this is how it looks.

I don't have my cord charger with me only my Anker charge box so I'm 100% sure it was never plugged back in. And some light usage after the restore so I dunno, this phone confuses me

Sent from my myTouch_4G_Slide using Tapatalk 2
 
Last edited:
cj chitwood

cj chitwood

Senior Member
Jun 7, 2009
612
79
Cowford, FL - OnePlus 7T running Res Remix 8.5.9
plus.google.com
Mine lost like 55% over about 7 hours last night. Come to find out, 100% of that loss was attributed to Cell Standby. Sure enough, I had no signal. The phone was also set for 2G only, which I never do. I was playing with settings earlier in the day, but I was sure I had set it back to 3G only via the notification bar.

I also experienced something I think I read a few pages (50 posts per page) back...

I had no signal, and was unable to get signal back. I tried unchecking the "2G Only" setting, but it wouldn't stick. I tried using the quick setting in the notebar, but that didn't change. I could not get it off of "2G Only" with no signal. I was afraid I would have to reflash another ROM like I saw a few other people post about. Then I got to thinking. If the phone doesn't have the SIM, it might not select *any* network mode, and "reset" what it's looking for. Turned out, whether or not I was right about how it works, I was right about the end result: I got signal back without flashing another ROM.

Power down the phone, pull the battery and SIM. Replace battery, power up phone without SIM. Uncheck 2G Only, power down phone. Remove battery, replace SIM and battery. Power up, and lo and behold 2G/3G mode with signal.

I'm pretty sure I have 2G network available where I am. So I'm not sure if it's because I lost signal on 2G-only mode or if it's because of a bug or a combination. I looked in my lolcat and saw absolutely nothing indicating a bug or other software issue.

I do wish, however, that instead of a checkbox to force "2G Only", we had a drop-down to select any of the multiple modes because the quick settings in the notification bar don't always work like we want (this was just such a case). Might help to force e.g. "3G-only" so the phone hardware doesn't even consider searching for nonexistent 2G.


EDIT: Just did it again. So apparently, going to 2G when you have no 2G signal can cause this to happen and it won't come out. I wonder if simply going to airplane mode would be an easier way to switch modes and then regain signal...


I have another question... When I'm charging the phone and I turn it off, it will not turn back on until either it's fully charged or I remove it from the charger. Anyone else notice this?
 
Last edited:
dillalade

dillalade

Senior Member
Sep 28, 2009
1,543
366
Richmond
strapped365 said:
*edit*
Kotedia?

Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse

Oops, fk knows how that got there - was adding a contact of that name. Disregard!



cj chitwood said:
The phone was also set for 2G only, which I never do. I was playing with settings earlier in the day, but I was sure I had set it back to 3G only via the notification bar.

I'm pretty sure I have 2G network available where I am. So I'm not sure if it's because I lost signal on 2G-only mode or if it's because of a bug or a combination.

I do wish, however, that instead of a checkbox to force "2G Only", we had a drop-down to select any of the multiple modes because the quick settings in the notification bar don't always work like we want (this was just such a case). Might help to force e.g. "3G-only" so the phone hardware doesn't even consider searching for nonexistent 2G.


EDIT: Just did it again. So apparently, going to 2G when you have no 2G signal can cause this to happen and it won't come out. I wonder if simply going to airplane mode would be an easier way to switch modes and then regain signal...
Click to expand...
Click to collapse

I have no such 2g/3g down time issues.
As for forcing 2g or 3g or a mixture.

Perhaps tweak your data widget options (see screenshot), to do exactly what you've asked for.
My usage with the notification widget is 100% functional.

Screenshot_2012-07-01-15-41-10.png


Again , I have no data problems. I switch between 2g & 2g/3g combo at will without loss of signal/data.

I'm in the UK on O2 network

Sent from my myTouch_4G_Slide using xda app-developers app
 
  • Like
Reactions: cj chitwood
mr.e.ferran

mr.e.ferran

Senior Member
Nov 28, 2010
73
9
Flashed alpha 5 over alpha 4 with no problems except a weird bug: when using ROM toolbox to change fonts the phone gets stuck in a weird bootloop. Battery pull and re-flashing fix it. Not a deal breaker but I like my sony sketch font

Sent from my myTouch_4G_Slide using Tapatalk
 
gtmaster303

gtmaster303

Senior Member
Oct 19, 2010
1,556
417
Just came from Virtuous Inquisition, and it's a very nice rom.
Only 1 minor annoyance I've had.

On my homescreen you will see that a link to an app always gets created and placed over my Fancy Widget on the home screen.
And the app drawer button in dock switches places with the messaging app.

How do I stop this from happening? Running Zeam Launcher. Everything else is exactly the same as when I was using Inquisition, and I had no problems like this.
 

Attachments

  • Screenshot_2012-06-30-16-07-53.jpg
    Screenshot_2012-06-30-16-07-53.jpg
    42.3 KB · Views: 165
You must log in or register to reply here.

Similar threads

kornyone
[ROM][Official]MyTouch4G Slide CyanogenMod 10 20130101 (Alpha 3) - 4.1.2
Replies
509
Views
92K
WeekendsR2Short
WeekendsR2Short
tbalden
[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16
Replies
412
Views
70K
OfficerJimLahey
OfficerJimLahey
kornyone
[ROM]MyTouch4G Slide CM7 SelfKang Alphafied Number 1 (11/1) - 2.3.7
Replies
727
Views
96K
WeekendsR2Short
WeekendsR2Short
Emmanuel U
|-ROM-|-4.0.4-|-AOKP-B39-|-CM9-|-6/15/12-|-WildchildIcE-v0.9b-|-Nightlies-|
Replies
1K
Views
112K
gtmaster303
gtmaster303
tbalden
[ROM][Feb 6 2012] Pyr-o-Ice ICS 1.0.2 (Android 4.0.3,AOSPish desensed)|Cam&Camcorder
Replies
1K
Views
140K
tbalden
tbalden

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 61
    kornyone
    kornyone
    CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.

    This is an alpha release, but you should find it stable for everyday use.

    Code: 
    #include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

    This is an alpha, with most critical functionality working.

    Working with Senior CyanogenMod team members, I brought TBalden into the project. TBalden has brought his large amount of Doubleshot experience to CyanogenMod Doubleshot porting, and together we have created (in very short order) a stable Alpha. TBalden created a team for maintenance of the Doubleshot with CyanogenMod going forward, "TeamDS".


    INSTRUCTIONS:
    - Upgrading from previous Doubleshot CM9 Alpha?
    1. It should be safe to flash the Alpha5 zip on top of previous alphas. DO backup your phone in case something goes wrong, but a wipe shouldn't be necessary coming from CM9 Alpha1.
    NOTE that the install wipes /system, so you may find you need to reflash gapps.

    - First time flashing CM 9 to your MyTouch4g Slide (or coming from another ROM)?
    1. Unlock/root your device and install Clockwork Recovery via ROM Manager.
    2. Do a Nandroid backup!
    3. WIPE
    4. Install the ROM
    5. Optionally install the Google Addon

    - Upgrading from earlier CM7?
    1. Follow instructions above. CM upgrade from CM7 Alpha1 will likely incur weird issues.


    HOW TO REPORT BUGS OR PROBLEMS?
    - Was your problem a hard reboot? Get us the file "/proc/last_kmsg".
    - Was your problem a soft reboot or a "boot loop"? Run "adb logcat" and get the full output.
    - Pastebin links preferred.
    - For now, please leave comments in the forums. TBalden and I will will be monitoring for activity as we continue to fix known issues.
    - Join #TeamDS on Freenode to talk to us directly.

    Direct download URL: http://www.jeago.com/doubleshot/cm-9-alpha6-doubleshot-signed.zip
    Alpha6 MD5: f9f0e4d95d7802e6ccb3b938b69ef7e0 . Build date 20120723.
    (hosted by Jeagoss of CyanogenMod, thanks!)


    You can find the latest CyanogenMod GAPPS CyanogenMod Wiki. Bottom of page, "CyanogenMod 9" GAPPS (latest works as of writing).

    Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

    As of Alpha4, Doubleshot source (device and kernel) has official open source CyanogenMod repos, with Gerrit access (https://review.cyanogenmod.com)

    ----- CHANGES -----

    Alpha6 Changelog (from Alpha5)
    - Updated kernel base to v3.0.36 from upstream AOSP branch.
    - Updated keylayout. TAB now mapped to ALT+TAB, www./.com functions properly.
    - Camera is no longer crashing (in our testing). This is from an upstream CM frameworks change.
    - Bluetooth wake lock is "fixed". When paired with handsfree audio, etc, and in standby, deep sleep works as expected.
    - Bluetooth tethering is functional, though not 100% yet.
    - Upstream changes in CyanogenMod. See http://review.cyanogenmod.com/#/q/status:merged,n,z for info on these Upstream changes.

    Please note that camera and bluetooth functionality are still a work in progress. In testing, we find more compatibility, less crashing, less power consumption overall. If you find steps to reproduce crashing, etc, please capture logs.



    The current buglist:
    - If you use Face Unlock, I have experienced an issue where sometimes the screen will go "dark" when attempting to unlock the phone, requiring a battery reset. This is infrequent, but only Face Unlock causes this problem.
    - Recording in camcorder @ 1080 doesn't work. (Other modes are fine, we have not removed 1080p from options yet).
    - Lights issues (more than one):
    -- Function keys on physical keyboard do not light up (CAPS/ALT), but the buttons work.
    -- Backlight on keyboard works most of the time, but can randomly go dark.
    - Random battery statistics issues. Not all people have this issue, it seems specific to the battery you use.
    - Google+ Hangouts do not work right now.
    - Very occasional radio (4g and sometimes bluetooth/wifi) dropoff/reset. Some have reports a SIM card message requesting power reset, which can be cleared by hitting back. Other times, turning data on/off resolves issue.


    Please note flashing someone else's kernel may ruin your experience with this rom and I advise against it. This rom was a joint effort between kornyone & tbalden. A LOT of core works for msm8660 was put in by many CM Team members, and much of our work is based on their: toastcfh, Kali-, Kmobs, Bumblebee, cretin45, and all of the rest of CM!

    You can get all of the Doubleshot source from the following URLs:
    https://github.com/CyanogenMod/android_device_htc_doubleshot/
    https://github.com/CyanogenMod/htc-kernel-doubleshot
    https://github.com/TeamDS/vendor_htc_doubleshot

    CyanogenMod source is available from CyanogenMod Github
    If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.

    http://code.google.com/p/teamds/issues/list


    (Added 5/11) Join us on freenode, #TeamDS, if you would like to chat about this rom or provide help with fixes.
    (Added 5/14) Updated to Alpha2.
    (Added 5/23) Updated to Alpha3
    (Added 6/8) Updated to Alpha4
    (Added 6/27) Updated to Alpha5
    (Added 7/23) Updated to Alpha6
    (Added 7/26) Added Bug tracker http://code.google.com/p/teamds/issues/list
    View
    29
    tbalden
    tbalden
    Please report issues here from now on: http://code.google.com/p/teamds/issues
    Be precise, add logcat if possible, details, how to reproduce etc etc etc


    NOTE:
    if you're S-On, then get the installer zip, extract the boot.img from the zip, and
    'fastboot flash boot boot.img' it, otherwise your kernel will be not updated and you wont be able to boot.
    Instructions http://xdaforums.com/showthread.php?t=1508556


    You can overclock and set cpu related stuff in Settings/performance

    cheers,
    enjoy!
    feel free to report stuff.

    Sixaxis controller test app reports that its compatible, so you might be able to use it with this ROM. Havent tested it myself with an actual device, i have no sixaxis device


    if interested here's a TotalCommander plugin that gives you access to your doubleshot MTP protocol device over the mtp usual windows browsing (known since gnexus), so you can copy files in Total Commander as well, not only in windows' built-in file browser.
    http://ghisler.fileburst.com/beta/wmdmplug.zip
    Download, enter the zip in TC, answer yes, to install it. Then you can access your sdcard files in Network filesystems/MediaAudio/myTouch_4G_Slide/SD Card/


    FIXES
    Till it gets merged into official repos/releases...

    Stefan's Trackpad wake flashable
    http://xdaforums.com/showpost.php?p=27132342&postcount=818
    View
    22
    tbalden
    tbalden
    seansc144 said:
    We believe in you T and korneyone

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

    thats nice!

    coz at last i've found the issue with screen wake.
    we're going to clean up stuff for an alpha 3 with kernel 3.0. don't expect it to happen in the next few days, we need more test, and kornyone is ATM rather busy with real life stuff. But rest assured, it's going to happen! :D

    summarized:
    - all functionality that was in alpha 2 is working
    - kernel issues resolved, deep sleep working now without tricks
    - kernel updated from 2.6 to 3.0.30, based on intervigil's pyramid (sensation) kernel tree
    - bonus: tethering stuff is working better now, needs more test
    - battery life better with deep sleep
    View
    21
    kornyone
    kornyone
    Official CM 9.1.0

    Ohhai!

    I don't have release notes for it yet, and I have not updated the OP.. .but....

    HTC Doubleshot has reached inclusion in the latest CyanogenMod 9 Release of 9.1.0! This marks the first time Doubleshot has been included in a major release, and is a milestone for the device. All previous releases have been "Self Kangs" or "Alphas" which I baked. This is the real thing :)

    Grab your copy from Get.CM -- http://get.cm/?device=doubleshot&type=stable

    Make sure you get the 9.1.0 release. The 9.0.0 release is mislabeled.

    More to come!
    View
    18
    tbalden
    tbalden
    We're evaluating the alpha3 build. It seems everything's fine (only minor issues we know of already), so you can expect it soon when we get it up on the official site.

    Sent from my myTouch_4G_Slide using Tapatalk 2
    View

New posts