I use Go launcher EX.
I don't know if this is relevant: I move every app to SD card.
g60madman suggested that I format the system and update from stock rom, so that's what I will try this time. Let me know if you also have any suggestion. Thanks.
I use go launcher also. I get some small issues that I'm not sure where they are coming from. I think I will look into this (if I stop customizing my build for a day). I may have seen this too.
I would try to use AWD for a couple of days to see if it's related. You shouldn't have to uninstall go launcher, just save the settings if you do. I've been playing with AWD today and I gotta say that it responds better IMO. I just like some of the features of go launcher. That, and it's what I've been using sense FroYo.
I use go launcher also. I get some small issues that I'm not sure where they are coming from. I think I will look into this (if I stop customizing my build for a day). I may have seen this too.
I would try to use AWD for a couple of days to see if it's related. You shouldn't have to uninstall go launcher, just save the settings if you do. I've been playing with AWD today and I gotta say that it responds better IMO. I just like some of the features of go launcher. That, and it's what I've been using sense FroYo.
I've just found the way to replicate the problem.
There is a game called "brain age test free."
Just open that game and exit out; the audible selection goes mute.
Works all the time and works on both Go launcher and AWD.
I also use go launcher because of some of its feature that I like.
Was just thinking...
Is there currently (and if not, could there be) a partial_wakelock called while in call?
Just a thought. May be way off base. Comments?
I think the proximity issue maybe resolved on r0.3 which I am currenntly running. There was a ton of updates on frameworks/base from Cynogenmod that I added into this build. I am going to test it some more of course, but as of right now it seems to be fixed (crossing fingers).
The Following 5 Users Say Thank You to g60madman For This Useful Post:
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
Quote:
Originally Posted by g60madman
Just for a little tease of whats to come in revision 0.3. Is it CM7, is it ICS, or is it MIUI?
Nice screenshots, but are you going to style the Google search bar to look like the one in ICS? And the notification area, don't forget that, too! Otherwise, great work. And thanks for responding to and fixing those bugs I reported.
Device(s): HTC One SV, Motorola Triumph (CM7.2), Motorola Droid X (ApeX)
Carrier: Boost
Thanks: 45
Thanked 7 Times in 6 Posts
Quote:
Originally Posted by MikeRL
Nice screenshots, but are you going to style the Google search bar to look like the one in ICS? And the notification area, don't forget that, too! Otherwise, great work. And thanks for responding to and fixing those bugs I reported.
That's a big concern to you?
__________________
Equality, rightly understood as our founding fathers understood it, leads to liberty and to the emancipation of creative differences; wrongly understood, as it has been so tragically in our time, it leads first to conformity and then to despotism.
Yes I do have the ICS search bar set as Mike listed. Sadly the proximity is still not working, was fine all day long after 12 calls and then this evening it started up again after I tested #13. I will be working on it this some more this weekend and do not plan to release until it's fixed!!!
Finally! The volume bug is fixed for me with this update!! Thank you!
I know you don't want to take full credit for the fix, but I wouldn't be enjoying it if you had not decided to resume development of CM7.
Nice work and I appreciate it.
__________________
The Commandments of Android
1) Open RAM is wasted RAM - Don't use Task Killers
2) Cheap devices are cheap for a reason. Don't expect high end performance.
3) Boot Loop = Wipe.
4) There are no viruses for android.
The Following User Says Thank You to TheBritton For This Useful Post:
Yes I do have the ICS search bar set as Mike listed. Sadly the proximity is still not working, was fine all day long after 12 calls and then this evening it started up again after I tested #13. I will be working on it this some more this weekend and do not plan to release until it's fixed!!!
Does anyone know of a CM7 build that doesn't have this bug. Just to be clear, sense there's two of them that seems to exist, the one where the phone would not turn back on after pulling away from the face. If you know of one (I'll be testing Tickerguy's builds next week) post is so someone else can confirm, please. If we can narrow if down, we may find where it got broken.
TG's ROMs, to make it easier to find them. I think that it was in those ROMs. I would love it some else could help with the testing part.
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
I would start by testing only Betas 1-4, since that's where the changelog says proximity issues were addressed at. What exactly do you mean is the issue with the proximity sensor? The screen turns off or the entire phone shuts down?
I would start by testing only Betas 1-4, since that's where the changelog says proximity issues were addressed at. What exactly do you mean is the issue with the proximity sensor? The screen turns off or the entire phone shuts down?
As far as I remember, I've been updating since TG's final version to Whyzor to g60, the proximity sensor issue has never been fixed. It works for a few times after initial updates, but it goes back again.
The proxitmity sensor issue is:
"when you move [the phone] away from your face during a call, screen stays off."
The screen suppose to back on automatically without having to push power button.
The Following User Says Thank You to viget For This Useful Post:
I'm on whyzor's 3/1 build (cause the old graphic driver works better on a couple games I'm playing.) I have "always use proximity" checked in call settings, one of the things I always do when first setting up cm7. I've been on this build for about a week now after a factory reset. I haven't the proximity issue at all. Today I made another 10 or so calls to an automated line purposefully to test for this issue. Proximity sensor worked each time. I'll keep making a lot of calls over the next days to see if I can get it to act up.
The Following User Says Thank You to Admack For This Useful Post:
g60, mind recompiling the whykernel/oc for me with this stepping table 64,122,245,460, 652,808,1024,1200,14**, 15** up to the highest ? id like to test it.
Last edited by PimpinEZ; April 29th, 2012 at 04:57 AM.
g60, mind recompiling the whykernel/oc for me with this stepping table 64,122,245,460, 652,808,1024,1200,14**, 15** up to the highest ? id like to test it.
If I have time I will look into it. I am still working on fixing the issue with the proximity and finishing up my final tweaks to r0.3
As far as I remember, I've been updating since TG's final version to Whyzor to g60, the proximity sensor issue has never been fixed. It works for a few times after initial updates, but it goes back again.
The proxitmity sensor issue is:
"when you move [the phone] away from your face during a call, screen stays off."
The screen suppose to back on automatically without having to push power button.
Yes I thought that was the case. I am testing out a change in the whyzor's kernel that's been around with TickerGuy. I am not sure this is the fix but this is a good starting point.
g60, mind recompiling the whykernel/oc for me with this stepping table 64,122,245,460, 652,808,1024,1200,14**, 15** up to the highest ? id like to test it.
If someone could tell me how to compile just a part of a ROM (I'm still mostly a cut and paster) I could handle requests like this.
Right now there is 61,122,245,576,768,1024,1113,1209,1305,1401,1516,1 612,1708,1804,1900,2016
What other frequencies would you want? I guess the inbetweens? Whyzor took them out because of the overhead that is caused by jumping to a higher frquency that isn't hight enough and needing to re-evaluate.
Last edited by dsmryder; April 29th, 2012 at 07:39 PM.
64,122,245,460, 652,808,1024,1200,14**, 15**
I like these because I can get a lower undervolt; furthermore, since most single core phones have a 600/800mhz CPUs I wanted those as steps for that range. I don't have a computer just this phone, so i was just curious if he had time to make a tweak.
Last edited by PimpinEZ; April 29th, 2012 at 08:24 PM.
Has anyone pulled the Kernel from the latest WIP 2.3.4 (4/29) and tried it in g60's CM7 to see if it enables HDMI?
ofcourse you would aslo have to edit this line in the build.prop
to
It has nothing to do with kernel, there is a lot of code that needs to be edited. I will be implementing wsimon's source for the HDMI in build r0.4. I don't plan to have it working as I need to spend some time with the code but I want to at least get his code into the build.
Here are the directories that need to be edited from the CM7 source code, and here is all the changes wsimon has done
It has nothing to do with kernel, there is a lot of code that needs to be edited. I will be implementing wsimon's source for the HDMI in build r0.4. I don't plan to have it working as I need to spend some time with the code but I want to at least get his code into the build.
Here are the directories that need to be edited from the CM7 source code, and here is all the changes wsimon has done
As far as I remember, I've been updating since TG's final version to Whyzor to g60, the proximity sensor issue has never been fixed. It works for a few times after initial updates, but it goes back again.
The proxitmity sensor issue is:
"when you move [the phone] away from your face during a call, screen stays off."
The screen suppose to back on automatically without having to push power button.
OK. I am on beta 1 right now, I'll report back if the contition exists on that one. I think it would be beneficial to everyone if some others who want this issue fixed to try beta 1 and say that they are so some others could report that they are tring beta2 and so on. If one persone does this, it can take a very long time.
Do you think you could explain what the camera fix is? I saw the post that originally mentioned it but I don't get what it does. Thanks.
Also, will it make any difference to me if I'm using a third party camera app?
Thanks again for your great work on this rom.
Basically all the fix does is when you take a picture the square icon that is focused will now turn green instead of the red. Makes sense that a picture taken would be green for good and red for bad.
The Following User Says Thank You to g60madman For This Useful Post:
The 360 Launcher is in Japaneses and this Indiana boy can't read it.
Just go through the setup by scrolling to the left and apply it. There is still some Japanese fonts listed but once the setup is configured it's almost all in English. This is being corrected with future builds. While it's not perfect it works a lot better than ADW in my humble opinion. The screen movements are more crisp and clean, and fades are more rich than before. Along with better themes than ADW offers including lock screens, memory management, battery management and such.
EDIT: If you really do not like it you can open the g60style.zip and delete the 360_Launcher_V2.2.1.apk located in system/apps and download ADW from the Play Store
Last edited by g60madman; April 30th, 2012 at 11:38 AM.
The Following User Says Thank You to g60madman For This Useful Post:
I don't have time to play today, but I hope it works. I had two calls and they both turned on the screen when I pulled the phone away frm my face. I did see the phone flashing thing during my second test call. I'll keep testing and wait for some confirmation to your fix before I give up.
I don't have time to play today, but I hope it works. I had two calls and they both turned on the screen when I pulled the phone away frm my face. I did see the phone flashing thing during my second test call. I'll keep testing and wait for some confirmation to your fix before I give up.
Yeah I tested 50 calls before I released this morning, pulling the phone away from my face multiple times during each call (sorry comcast). Also did multiple reboots just to verify it wasn't a fluke. It seems to be OK right now.
The Following User Says Thank You to g60madman For This Useful Post:
So, if I have wyzor's ROM installed currently, and want to use this one, can I just flash it on top of wyzor's, or do I have to do a data wipe first? If I have to do a data wipe, is there any way I can backup the apps I have installed using something like Go Backup first, and restore them after flashing this rom?
So, if I have wyzor's ROM installed currently, and want to use this one, can I just flash it on top of wyzor's, or do I have to do a data wipe first? If I have to do a data wipe, is there any way I can backup the apps I have installed using something like Go Backup first, and restore them after flashing this rom?
Sorry, I'm kind of new to the whole ROM'ing jazz.
You just need to format the cache & then format the dalvik cache. Install the ROM and then install the gapps. I just did it for my friends Triumph this morning and it worked fine (he was still on Whyzor's ROM). I am sure the same would be the same if your coming from TickerGuy's ROM.
OK. I am on beta 1 right now, I'll report back if the contition exists on that one. I think it would be beneficial to everyone if some others who want this issue fixed to try beta 1 and say that they are so some others could report that they are tring beta2 and so on. If one persone does this, it can take a very long time.
So, who's wit me!
Let me try b0.3. If it still does it, I try want I can do.
Im thinking about trying this out again as opposed to CM9, what file do I need to get out of my backup to save my messages? I will most likely copy that file from my cm9 backup and restore to my old cm7 backup then upgrade from there.
Im thinking about trying this out again as opposed to CM9, what file do I need to get out of my backup to save my messages? I will most likely copy that file from my cm9 backup and restore to my old cm7 backup then upgrade from there.
Thanks!
What messages are you talking about email or text/sms?
Yeah, you're right that the launcher is better. I just wish we had someone here who knew Japanese so that we could translate it over...
The forum which I linked on the first post is working on adding more English to it. Sadly the download area may never be fixed since it links to the remote site. While I was working on building the r0.3 ROM and putting the final fixes on it, a newer version of the 360 launcher 2.3 was released which I didn't see till this morning . The next ROM I release will have the new version. Even though there is some Japanese language barriers in the launcher I don't think it takes away from the usability as there is enough English in it to enjoy the launcher.
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
Problem is that the 360 Browser is completely in Chinese. Maybe we should try and remove it as a download option? It is useless unless you can read Chinese. That browser is about 99% in Chinese.
Last edited by MikeRL; April 30th, 2012 at 04:02 PM.
I haven't looked at the browser LOL I will check into it and see if I can remove it from the apk. I will also see if I can't get the source code so I can just build it from source during the build.
The Following User Says Thank You to g60madman For This Useful Post:
I can't get the volume fix to work. In build 0.2 I could pause for 5 seconds when the bug occurred and it went back to full volume every time without fail.
Today I flashed the new Codename Android rom briefly, went back to 0.2 and it didn't work. Now on 0.3 it still doesn't work...
I loved you for what you'd done when it was working. Help, someone!
Device(s): HTC One SV, Motorola Triumph (CM7.2), Motorola Droid X (ApeX)
Carrier: Boost
Thanks: 45
Thanked 7 Times in 6 Posts
I couldn't figure this out with CM7 TGR either but when my brightness is set to auto and the screen is off, when I press the unlock key, the screen stays dim for about 3 seconds before it is normal brightness. Is there a way to make the screen normal brightness immediately?
Device(s): HTC One SV, Motorola Triumph (CM7.2), Motorola Droid X (ApeX)
Carrier: Boost
Thanks: 45
Thanked 7 Times in 6 Posts
One other more serious thing...
In the past when I've installed fresh ROMs, I could open Google Play and Tapatalk would be a purchased download so I would never have to pay since my original purchase. Now, when I open My Apps, all of my previously downloaded apps are listed but Tapatalk is $2.99.
ETA:
Never mind, I cleared the cache and Data of the Google Play app and all is well now when I reopen it.
Last edited by sqwerl; April 30th, 2012 at 05:09 PM.
The Following 2 Users Say Thank You to sqwerl For This Useful Post:
56Likes
Comments?
. The next ROM I release will have the new version. Even though there is some Japanese language barriers in the launcher I don't think it takes away from the usability as there is enough English in it to enjoy the launcher.
