• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][ALPHA] Triumph CM9 v0.6.17.0 [FINAL]

Running 0.6.0 w/o /system/bin/btwlancoex and w/ apex launcher. GPS is Working!!! (2min for as cold start GPS lock-on inside) New Daily Driver!!! Thanks to all you guys developing this. ICS!!!!

EDIT: and the navigation voice is better in ICS!!!

EDIT: Remote install market response is sooooooo much faster in ICS.
 
TrueJournals said:
I've been running CM9 all of today to help out with testing and hopefully provide some real-life bug reporting, and I noticed something with my data connection. It seems that the data connection will work fine, but stop working if the phone goes to sleep for a bit. When woken back up, the data connection doesn't resume correctly, and I have to toggle airplane mode to regain working data.

Essentially, I'll have my phone in my pocket for an hour or two, then try to use it. I'll notice that my signal bars are grey instead of blue, and I get no "up/down" transfer animation like I normally do. Any attempt to use the data connection at this point simply fails. Like I said, this is fixed by toggling airplane mode.

The only thing that seems like it might be related in my logcat is:
Code: 
F/NetworkStats( 3327): problem reading network stats
F/NetworkStats( 3327): java.lang.IllegalStateException: problem parsing idx 1
F/NetworkStats( 3327): 	at com.android.internal.net.NetworkStatsFactory.readNetworkStatsDetail(NetworkStatsFactory.java:300)
F/NetworkStats( 3327): 	at com.android.server.NetworkManagementService.getNetworkStatsUidDetail(NetworkManagementService.java:1282)
F/NetworkStats( 3327): 	at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:831)
F/NetworkStats( 3327): 	at com.android.server.net.NetworkStatsService.performPoll(NetworkStatsService.java:799)
F/NetworkStats( 3327): 	at com.android.server.net.NetworkStatsService.access$100(NetworkStatsService.java:128)
F/NetworkStats( 3327): 	at com.android.server.net.NetworkStatsService$3.onReceive(NetworkStatsService.java:633)
F/NetworkStats( 3327): 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:728)
F/NetworkStats( 3327): 	at android.os.Handler.handleCallback(Handler.java:605)
F/NetworkStats( 3327): 	at android.os.Handler.dispatchMessage(Handler.java:92)
F/NetworkStats( 3327): 	at android.os.Looper.loop(Looper.java:137)
F/NetworkStats( 3327): 	at android.os.HandlerThread.run(HandlerThread.java:60)
F/NetworkStats( 3327): Caused by: java.io.FileNotFoundException: /proc/net/xt_qtaguid/stats: open failed: ENOENT (No such file or directory)
F/NetworkStats( 3327): 	at libcore.io.IoBridge.open(IoBridge.java:406)
F/NetworkStats( 3327): 	at java.io.FileInputStream.<init>(FileInputStream.java:78)
F/NetworkStats( 3327): 	at com.android.internal.net.NetworkStatsFactory.readNetworkStatsDetail(NetworkStatsFactory.java:269)
F/NetworkStats( 3327): 	... 10 more
F/NetworkStats( 3327): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
F/NetworkStats( 3327): 	at libcore.io.Posix.open(Native Method)
F/NetworkStats( 3327): 	at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
F/NetworkStats( 3327): 	at libcore.io.IoBridge.open(IoBridge.java:390)
F/NetworkStats( 3327): 	... 12 more

I'll see if I can get a better logcat later for someone to examine.
Click to expand...


I had this issue on one of my old phones with a custom ROM (can't remember which one), but I used this app to "fix" it until the dev did: Connection Checker.

It seems that data has only gone down once on my phone in ~16 hrs since I installed the app (the app logs data changes). So not sure if it is actually a problem or not...
 
phohammer said:
I had this issue on one of my old phones with a custom ROM (can't remember which one), but I used this app to "fix" it until the dev did: Connection Checker.

It seems that data has only gone down once on my phone in ~16 hrs since I installed the app (the app logs data changes). So not sure if it is actually a problem or not...
Click to expand...

Hmmm... looks interesting! I'll give it a shot, thanks! :)
 
This might be a noob question, but with development going like crazy on this ROM, is there a way to just keep flashing the latest ROM, retaining all settings? So far I've just been using Titanium Backup, but that can be a little time consuming. Thanks in advance! I love this ROM! It's my daily driver even without stuff working at the moment.
 
BlurryEyed said:
This might be a noob question, but with development going like crazy on this ROM, is there a way to just keep flashing the latest ROM, retaining all settings? So far I've just been using Titanium Backup, but that can be a little time consuming. Thanks in advance! I love this ROM! It's my daily driver even without stuff working at the moment.
Click to expand...

Titanium backup can cause problems occasionally. Just make a NANDroid backup of the ICS ROM before switching back to your daily ROM. When a new version comes out, restore the ICS ROM, wipe cache & dalvik-cache, flash new ROM + Gapps (needed step for now), reboot & it should have your old ICS settings with new version.
 
Whyzor said:
Titanium backup can cause problems occasionally. Just make a NANDroid backup of the ICS ROM before switching back to your daily ROM. When a new version comes out, restore the ICS ROM, wipe cache & dalvik-cache, flash new ROM + Gapps (needed step for now), reboot & it should have your old ICS settings with new version.
Click to expand...


Exactly what I have been doing
 
BlurryEyed said:
This might be a noob question, but with development going like crazy on this ROM, is there a way to just keep flashing the latest ROM, retaining all settings? So far I've just been using Titanium Backup, but that can be a little time consuming. Thanks in advance! I love this ROM! It's my daily driver even without stuff working at the moment.
Click to expand...
Don't do a full wipe between flashes.

If you don't do a clean install it may cause issues sometimes depending on what is changed. If you have a problem though, you should always do a clean install and make sure that isn't the issue.
 
Whyzor said:
Titanium backup can cause problems occasionally. Just make a NANDroid backup of the ICS ROM before switching back to your daily ROM. When a new version comes out, restore the ICS ROM, wipe cache & dalvik-cache, flash new ROM + Gapps (needed step for now), reboot & it should have your old ICS settings with new version.
Click to expand...

I've experienced the Titanium backup issue. It works fine if I just restore Apps w/settings, but I do everything, stuff breaks and I have to restore from backup. Thanks for the tip, I'll try that.
 
Whyzor said:
Try deleting the "/system/bin/btwlancoex" file, wasn't sure if that was needed yet in CM9. If it works, then my CM7 commit should also be applied to CM9:
Click to expand...

I don't know how to do most of this programming stuff (although I've been reading and learning along with my C++ class at college). Is there anyway we could get this fix put into the ROM so everyone can use it? That would be awesome devs. And as always. I'll be patient. Just whenever you can.
 
ajbuck68 said:
I don't know how to do most of this programming stuff (although I've been reading and learning along with my C++ class at college). Is there anyway we could get this fix put into the ROM so everyone can use it? That would be awesome devs. And as always. I'll be patient. Just whenever you can.
Click to expand...

Open the downloaded ROM zip file, go to system/bin and delete the file. Then, flash the zip, like you do normally. It's as simple as that ;)
 
So is it just me or does the trebuchet launcher kinda suck? And let me add this is in no way a negative comment toward the devs. U guys kick much ass and I sincerely appreciate all of your efforts. I urge people if they're having problems with the launcher like lagging, freezing and such, go over to xda and download apex launcher. There's actually a thread on this site containing the links for apex and nova launcher. I've tried both and apex definitely is the apex of ics launchers so far. Check it out.
 
Whyzor said:
Titanium backup can cause problems occasionally. Just make a NANDroid backup of the ICS ROM before switching back to your daily ROM. When a new version comes out, restore the ICS ROM, wipe cache & dalvik-cache, flash new ROM + Gapps (needed step for now), reboot & it should have your old ICS settings with new version.
Click to expand...

Worked like a charm. Thanks Whyzor!
 
ajbuck68 said:
I don't know how to do most of this programming stuff (although I've been reading and learning along with my C++ class at college). Is there anyway we could get this fix put into the ROM so everyone can use it? That would be awesome devs. And as always. I'll be patient. Just whenever you can.
Click to expand...

Yes the fix will be included in the next build once Mantera gets to it tonight. My original post was to see if it actually works for people in CM9.
 
dg61981 said:
So is it just me or does the trebuchet launcher kinda suck? And let me add this is in no way a negative comment toward the devs. U guys kick much ass and I sincerely appreciate all of your efforts. I urge people if they're having problems with the launcher like lagging, freezing and such, go over to xda and download apex launcher. There's actually a thread on this site containing the links for apex and nova launcher. I've tried both and apex definitely is the apex of ics launchers so far. Check it out.
Click to expand...

IMO it sucks as well... But you have to remember cm9 is a work in progress so the cyanogenmod team haven't got all the bugs and stuff out yet.
 
BlurryEyed said:
This might be a noob question, but with development going like crazy on this ROM, is there a way to just keep flashing the latest ROM, retaining all settings? So far I've just been using Titanium Backup, but that can be a little time consuming. Thanks in advance! I love this ROM! It's my daily driver even without stuff working at the moment.
Click to expand...


Just flash it with the current os. When it boots it will upgrade the applications and settings for the new update. It kinda reminds me of windows when updating it and restarting.
 
agentc13 said:
Don't do a full wipe between flashes.

That can cause issues sometimes depending on what is changed. If you have a problem though, you should always do a clean install and make sure that isn't the issue.
Click to expand...

Is this true? Doing a full wipe and clean install can cause problems? I always thought it was the other way around: a full wipe/clean install is always fine, but upgrading the rom without wiping can occasionally cause issues, depending on what was changed.
 
You must log in or register to reply here.
Back
Top Bottom