Hey guys, i installed AOKP cm9 Monday night and once installed i fell in love. I came from th eclipse rom which was good but just the customization and look of AOKP is beautiful.
SO this leads me to my problems. When i flashed the rom and used it yesterday it was pretty much working great. I didnt use the dialer much so i dont know if t was happening then or just started. It seems if i call someone and the screen goes black due to the proximity sensor it will not come back after to end the call or when i pull the phone away from my face. I have to constantly press the power button to unlock the phone then i can click end then the screen locks again and have to swipe unlock to get back into the phone. This is a major PITA and wondering if it is a known bug or am i the only one.
Also from looking at the official thread here it states the camera is working but mine does not.
NVM just got it going
Also wondering when i was using elclispe and would go into rom toolbox > build.prop tweaks i could adjust about 7 things such as prox sensor and such. Now i only have 4 lcd, ring delay vmheap, scan interval. Why do i only get 4 tweaks versus the 7 i had before.
Add: Also i just noticed now when i get a call my screen stays blank. I had to again click the power button x amount of times to get in and now recieving a message "processcom.android is not responding. would u like to close it"
Ugghh this is so aggrevating
lso noiced in apps running im using at the highest 330-350 mb and states betwee 48-90mb free. thats to high isnt it
jeff5347 said:
Hey guys, i installed AOKP cm9 Monday night and once installed i fell in love. I came from th eclipse rom which was good but just the customization and look of AOKP is beautiful.
SO this leads me to my problems. When i flashed the rom and used it yesterday it was pretty much working great. I didnt use the dialer much so i dont know if t was happening then or just started. It seems if i call someone and the screen goes black due to the proximity sensor it will not come back after to end the call or when i pull the phone away from my face. I have to constantly press the power button to unlock the phone then i can click end then the screen locks again and have to swipe unlock to get back into the phone. This is a major PITA and wondering if it is a known bug or am i the only one.
But for the life of me, trying to use the dialpad was nearly impossible while on a call. That helped ALOT. You can also DL Screeble in the market. That will help.
Also from looking at the official thread here it states the camera is working but mine does not.
NVM just got it going
Also wondering when i was using elclispe and would go into rom toolbox > build.prop tweaks i could adjust about 7 things such as prox sensor and such. Now i only have 4 lcd, ring delay vmheap, scan interval. Why do i only get 4 tweaks versus the 7 i had before.
Add: Also i just noticed now when i get a call my screen stays blank. I had to again click the power button x amount of times to get in and now recieving a message "processcom.android is not responding. would u like to close it"
Ugghh this is so aggrevating
Click to expand...
Click to collapse
I have the same problem on my X2. You gotta go into settings and I forget where at the moment, but you have to enable hysterisis or something to that extent. I kick myself for not remembering.
As for ROM toolbox, don't use it.
COme on man you gotta remember haha what does hyterisis do and why not use rom toolbox
Sorry about that. Had to look up where DZK gave me some insight on that:
dragonzkiller said:
In CM9 (and I believe CM7) there is a setting under the brightness controls (I believe it's there, I don't have either running right now) called "hysteresis." Hysteresis is basically a "smoothing out" of what the light sensor sees and what value is actually sent to the brightness controls. Enabling that will make the screen react slower to changing light situations, but will disable (or should disable) flicker of the screen from the light sensor acting up. It might not be the problem, but it shouldn't hurt to try it out.
Click to expand...
Click to collapse
Also for CM7, I know you said you are on CM9, it says in the original post:
"16. Never user RomManager! (Yes it's included, but that's a CM7 thing and won't work with the DX2.)"
I've also read other areas that ROM manager is a no-no for the X2. Better to be safe than sorry.
Thanks Tally. I found where to play with hysteria and it was getting better but still doing it. I had my display or auto, for the phone to adjust display depending on the light. I turned that off and left it at 80% no matter the light and that fixed it. Wow just the auto brightness display could cause so much crap.
So i should just uninstall Rom manager, I dont usually use it anyways.
You stated in your previous post rom toolbox. Was it toolbox or manager that u are stating we shouldnt use?
Also is 300-350mb of ram ok for the phone to be using fairly regularly?
spoke to soon. It was working now its back to normal. I am ready to bodyslam this phone
Tally.. what settings did you do on your d2 to make it work correctly
Don't do it. Mine was doing exactly what you have described. Once you get it figured out, its ok. But yes... it will make you want to punt it across the room.
Your 300-350 mb of ram is ok.
I wouldn't delete it ROM manager. Just leave it as it is.
---------- Post added at 01:22 PM ---------- Previous post was at 01:12 PM ----------
I had the best luck running CM9 mashed up- not supercharged or anything else. Others here had some luck with the V6 supercharger. Different phones just acted differently. But now that the beta version has the mash up in the build.prop just let it ride. Avoid Facebook and sites that have alot of media to load.
It really does work pretty good once you get a feel of how your phone reacts to it. Alot of the things are tolerable.
What do u mean by mashed up. Do you mean by cm9 or the aokp cm9. I am getting some really wacky stuff happening. System running real slow, screen not coming on usually from a call or sometimes when trying to unlock phone, now my VM wouldn't respond, apps taking a lot more time than usual to open. I don't know if this is the aokp from or the phone. I had the screen glitch w eclipse but not all the other stuff. I called verizon and they r willing to send out a replacement but just not sure if its the phone or rom
ok so this is weird and not sure if it is the problem. I was trying to play with anything that may affect how slow it is and once i flashed the aokp rom i downloaded a little later a cobalt theme for my theme chooser. Was running that all day and just now said " let me try putting it back to system theme" once the system them was in and everything loaded it was back to working quick again.
Now be it , it has only been a half hour but already it is what i saw first thing and the screen glitch is there but i can end calls w the power button. Would a theme make the phone act wacky?
jeff5347 said:
What do u mean by mashed up. Do you mean by cm9 or the aokp cm9. I am getting some really wacky stuff happening. System running real slow, screen not coming on usually from a call or sometimes when trying to unlock phone, now my VM wouldn't respond, apps taking a lot more time than usual to open. I don't know if this is the aokp from or the phone. I had the screen glitch w eclipse but not all the other stuff. I called verizon and they r willing to send out a replacement but just not sure if its the phone or rom
Click to expand...
Click to collapse
Mashup is a flashable add on for roms. It is supposed to make things run smoother and help with the signal. Mashup is pre installed on CM9 alpha 5 and beta 1, I don't believe AOKP comes with it but Im not sure. And I had a bunch of issues with CM9, but Ive been running CM7 for months and love it. Maybe give CM7 a shot till the new ICS roms get debugged a little more.
Ok first off dont ever talk to verizon about your issues, always come to the forums... Always. Verizon doesn't know anything beyond complete stock. You need to spend time looking around the x2 forums read read read. Mashup is a mod that's right here in our dev forum very easy to apply just download the right version and flash in the appropriate recovery
Rolling AOKP in the north.
Related
A week ago I Odin'd back to stock and upgraded to the official 2.2 VIA Kies Mini. I have not rooted since or really even restored any of my old apps. No mods, just a stock Vibrant now. While I was playing WordFeud the phone locked up for about 20 to 30 seconds then on the screen it stated a screenshot has been taken. I then checked the Gallery and sure enough there was a picture of the screen. My question is has anyone seen this or know what happened. I checked the WorFeud app help and it didn't mention anything about a screen capture feature. Is there some sort of button combination on the new 2.2 Release that allows for screen captures to be taken? I was pretty confused by this, please let me know your thoughts and/or experiences.
OK, I see others have encountered this too and I would of found that if I searched correctly, as in spell correctly. OK, I see that people are saying to hold the back button and hit the home or menu button. I have tried these methods and have yet to make it work again. Either way, since this is sort of covered already, without a clear answer though, MODS feel free to delete.
Crap, didn't see your thread.
I encountered the same thing today and it was pretty nice. Still trying to figure out how to do it. Its a nice feature!
I did it too....im not rooted at this time. Cant figure it out.....
Sent from my SGH-T959 using XDA App
Yeah I've done that too accidentally. Don't know how though.
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
I ended up with screen shots in my gallery and I have no idea how they got there. There was never a notification or anything.
There is something built in, but I don't think the Vibrant really supports multitouch on the capacitive buttons. My girlfriend can do this on command, but only in the mms app. She clicks back, and when she feels a delayed haptic feedback, she pushes home and it works everytime.
Sent from my SGH-T959 using XDA App
Yes I have had the same thing happen, it definitely a timing thing I tried to master but only get 10% effective so I stay with shoot me,, just a weird glitch in the phone
roumenjr said:
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
Click to expand...
Click to collapse
Yeah, I was rocking Macnut R14 for a while after trying a few others. I updated to Samsung 2.2 to test out because a friend was thinking of trying it and asked if I would try it first. I was bored of it within a hour I think but gave it a few days. Bionix and DOW Kernal on it now.
I have been using the same rom since the day I received my Galaxy Note so I am used to it by now since I have been using it for over four months. I even flashed a couple other Gingerbread roms which were nice but I came back to the Solaris Prime rom qickly after flashing. After waiting since the first ICS leak I got bored and flased a custom ICS rom with the intention of playing with it for a while then flashing back to Gingerbread. The screen was bright on every Gingerbread rom I flashed, but on the ICS rom I flashed it was nowhere near as bright. I always use full brightness and never use auto adjust which is what I set it to on the ICS rom. This is the ICS rom I tried out http://forum.xda-developers.com/showthread.php?t=1686320 Now my question is, has anyone else noticed this or is it maybe only a problem with this rom? Are ICS roms not as bright as Gingerbread roms cause I need the screen to be very bright? I noticed the brightness was very dim compared to Gingerbread roms I have used within five seconds of setting the brightness to full and turning off auto adjust. If all the ICS roms are like this I think I will stay with Gingerbread cause this is a deal breaker for me.
EDIT: I figured it out. It is the Auto Adjust Screen Power setting, when checked the screen becomes dim when unchecked the screen is vived and bright. I guess this setting is not in all roms.
Hard to compare since I can only load one ROM at a time. But I never noticed the difference in brightness. I leave mine turned up also as I am frequently outside with my work and play. The 15 toggle mod is not somehow overiding your brightness setting in ICS?
I believe I have noticed the same issue. I thought maybe it was just me, but apparently I am not the only one. I am rooted and running BlackStar rom right now, and I can compare it side by side with my girlfriends stock unrooted note and hers seems noticeably brighter. But even that I chalked up to her not having a screen protector and me having one. But I wouldn't think the screen protector would inhibit the brightness much if at all.
I also have gotten to the point of using full brightness, becuase auto brightness is unusable at times, even indoors.
Are we the only 2? LOL. I have noticed another issue with the backlight today. The screen seemed dim, but every once in a while would get bright for like half a second then go back to dim. I have it set to full brightness, but I tried covering the sensor, or at least what I think is the sensor(gonna have to google that) and it didn't change anything.
mike208 said:
I believe I have noticed the same issue. I thought maybe it was just me, but apparently I am not the only one. I am rooted and running BlackStar rom right now, and I can compare it side by side with my girlfriends stock unrooted note and hers seems noticeably brighter. But even that I chalked up to her not having a screen protector and me having one. But I wouldn't think the screen protector would inhibit the brightness much if at all.
I also have gotten to the point of using full brightness, becuase auto brightness is unusable at times, even indoors.
Click to expand...
Click to collapse
Well did you compare when you both stock? Not every screen is created equally. I've seen identical phones next to each other and both have completely different temperatures on the screen (one bluish and one yellowish).
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
porkenhimer said:
I have been using the same rom since the day I received my Galaxy Note so I am used to it by now since I have been using it for over four months. I even flashed a couple other Gingerbread roms which were nice but I came back to the Solaris Prime rom qickly after flashing. After waiting since the first ICS leak I got bored and flased a custom ICS rom with the intention of playing with it for a while then flashing back to Gingerbread. The screen was bright on every Gingerbread rom I flashed, but on the ICS rom I flashed it was nowhere near as bright. I always use full brightness and never use auto adjust which is what I set it to on the ICS rom. This is the ICS rom I tried out http://forum.xda-developers.com/showthread.php?t=1686320 Now my question is, has anyone else noticed this or is it maybe only a problem with this rom? Are ICS roms not as bright as Gingerbread roms cause I need the screen to be very bright? I noticed the brightness was very dim compared to Gingerbread roms I have used within five seconds of setting the brightness to full and turning off auto adjust. If all the ICS roms are like this I think I will stay with Gingerbread cause this is a deal breaker for me.
Click to expand...
Click to collapse
The devs on custom roms turn down the brightness due to ocer heating..even if u can move the bar all the way to bright its still not the same
Sent from my SAMSUNG-SGH-I717 using xda premium
erick161 said:
Well did you compare when you both stock? Not every screen is created equally. I've seen identical phones next to each other and both have completely different temperatures on the screen (one bluish and one yellowish).
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
This is not anything that I needed to compare. It was noticable and since it happened I have read about other devices having the same issue after upgrading to ICS. It seem like the only devices this happens with are Samsung devices cause every device I found with this issue was a Samsung device. Not sure if they are putting a limit on brightness cause I know a lot of people said the contrast was too high on the Note but there is clearly something making the screen look washed out with ICS. I want my screen to be bright like it is capable of. I want my whites to be white like they are on Gingerbread.
erick161 said:
Well did you compare when you both stock? Not every screen is created equally. I've seen identical phones next to each other and both have completely different temperatures on the screen (one bluish and one yellowish).
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
This is not anything that I needed to compare. It was noticable and since it happened I have read about other devices having the same issue after upgrading to ICS. It seem like the only devices this happens with are Samsung devices cause every device I found with this issue was a Samsung device. Not sure if they are putting a limit on brightness cause I know a lot of people said the contrast was too high on the Note but there is clearly something making the screen look washed out with ICS. I want my screen to be bright like it is capable of. I have also read lots of people sayin that for some reason after rooting ICS their screens are not as bright but they cannot figure out why rooting would cause this to happen.
JB calhoun said:
The devs on custom roms turn down the brightness due to ocer heating..even if u can move the bar all the way to bright its still not the same
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
That makes no sense. I need a dev to tell me they limit the brightness we can use before I would beleive that. And not only that the problem seems to be happening on official firmware upgrades not just custom roms. I do not think its a coincidence that all the devices I have found this problem happening on after updating to ICS were Samsung devices.
I recreated the problem so people can see it happening on their devices. Try this
1: Turn full brightness on and turn off auto adjust.
2: Open the default browser, and Gmail and leave them running.
3: Now go to home and long press the home button and the app icons will popup. Pay attention to Gmail and the browser, and you will notice the task manager icons are much brighter than the apps.
4: Without taking your eyes off the task icons open the browser and you will notice it gets dimmer then the task icons.
5: Now hit the menu button and when it pops up the browser will get brighter. Hit it again it will get dimmer.
6: Now hit the tab button and you will also see the tab icon is much brighter than the app itself.
I have noticed the apps that have the black menu popup get lighter and darker when you push the menu button but the ones with the white menu popup stay the same when you push the menu button. The weird thing is it seems like the system menus, app menus and the launcher are all as bright as they should be its just the actual apps that are washed out. I have only tried two AOKP roms so maybe this is a problem with those roms but it is very noticeable especially on apps that have white backgrounds. I cannot figure out why the whole system is bright til I open an app then the app gets dimmer then the rest of the system.
Lol
Sent from my SAMSUNG-SGH-I717 using xda premium
This ICS rom I'm using (FJ ucle2#6...is not "darker" per sey .
I'm leaning more toward darker theme features perhaps ?
But I prefer the dark background popups with white letters etc. And I suppose it's possible that the ICS leaks are reduced to improve battery life ?
I honestly can't say, but I do know that my stock GB was like looking into the sun at night for me.
My eyes don't do bright very well ....g
I have the same problem!!!
I use my Galaxy Note (ATT) at full brightness and I have had it for 4 months. Got bored and decided to root it yesterday and installed an ICS rom. The screens were noticeably darker even at full brightness. It was depressing me and I wanted to go back to Gingerbread, but the MDSUM of my nand backup was incorrect for some reason, so I have not been able to do that. Looking around now for some Gingerbread roms to flash today!!!
ariot said:
I have the same problem!!!
I use my Galaxy Note (ATT) at full brightness and I have had it for 4 months. Got bored and decided to root it yesterday and installed an ICS rom. The screens were noticeably darker even at full brightness. It was depressing me and I wanted to go back to Gingerbread, but the MDSUM of my nand backup was incorrect for some reason, so I have not been able to do that. Looking around now for some Gingerbread roms to flash today!!!
Click to expand...
Click to collapse
Try this Gingerbread rom its great http://forum.xda-developers.com/showthread.php?t=1563390
porkenhimer said:
Try this Gingerbread rom its great http://forum.xda-developers.com/showthread.php?t=1563390
Click to expand...
Click to collapse
Thank you!
porkenhimer said:
Try this Gingerbread rom its great http://forum.xda-developers.com/showthread.php?t=1563390
Click to expand...
Click to collapse
Just an FYI, - I was downloading another rom from the same team as the one you recommended when I saw your update, so I went ahead and flashed the one I already downloaded. Took me back to 2.3.6, but it did NOT fix my screen brightness issue. I therefore went ahead and took my phone completely back to stock,unrooted and it's all good now.
ariot said:
Just an FYI, - I was downloading another rom from the same team as the one you recommended when I saw your update, so I went ahead and flashed the one I already downloaded. Took me back to 2.3.6, but it did NOT fix my screen brightness issue. I therefore went ahead and took my phone completely back to stock,unrooted and it's all good now.
Click to expand...
Click to collapse
Thats the rom I use and its super bright. Try it out I promise you will like it.
just pointing out - I agree about the brightness thing.
specially so in my favorite new rom, the latest from team perfection (the one released at the end of june 2012). it's an amazing rom, but it is quite dramatically dimmer in autobrightness modes than GB roms and is in fact so fim in autobrightness modes that I can't see it very well with my old eyes. I had no problem with other roms, and the stock gb rom is MUCH bright in auto mode.
then I take it out of autobrightness and go outside in the sun. it's almost unreadable in the sun outdoors (walking around). reverted to stock nandroid in autobrightness mode - I can read it ok in the sun. reverted to nandroid of the new ics rom. crank the brightness, can't read it, autobrightness is no brighter (maybe even dimmer) in the sun.
this isn't acceptible - the display on the note is amazing, why take away one of the best features of the note?
I cant' even use the phone in the sun when walking now.
I hope someone can find a way to change the brightness levels after the fact - that would be a really helpful tweak for those of us who can easily tell the difference (between readable and unreadable) in our roms.
I've looked through build.prop files but can't see anything there obviously related to screen brightness, so it must be something in teh roms or kernels.
cheers
Don
dkelley said:
just pointing out - I agree about the brightness thing.
specially so in my favorite new rom, the latest from team perfection (the one released at the end of june 2012). it's an amazing rom, but it is quite dramatically dimmer in autobrightness modes than GB roms and is in fact so fim in autobrightness modes that I can't see it very well with my old eyes. I had no problem with other roms, and the stock gb rom is MUCH bright in auto mode.
then I take it out of autobrightness and go outside in the sun. it's almost unreadable in the sun outdoors (walking around). reverted to stock nandroid in autobrightness mode - I can read it ok in the sun. reverted to nandroid of the new ics rom. crank the brightness, can't read it, autobrightness is no brighter (maybe even dimmer) in the sun.
this isn't acceptible - the display on the note is amazing, why take away one of the best features of the note?
I cant' even use the phone in the sun when walking now.
I hope someone can find a way to change the brightness levels after the fact - that would be a really helpful tweak for those of us who can easily tell the difference (between readable and unreadable) in our roms.
I've looked through build.prop files but can't see anything there obviously related to screen brightness, so it must be something in teh roms or kernels.
cheers
Don
Click to expand...
Click to collapse
I mentioned this on one if the rom threads and they got mad for some reason. They acted like I was making the issue up. I do not know how I noticed the ICS roms are not as bright as the Gingerbread roms but not many others have noticed. It is insanely evident that the ICS roms do not match up in brightness when compared to Gingerbread. I have also searched the web about the issue and all the devices with this problem are made by Samsung. The big bright screen should not suffer with an upgrade. I want my screen to be just as bright on ICS as it is on Gingerbread. With this issue ICS is a big turn off for me. I am beginning to think that all the reports of over saturation on the screen of newer Samsung devices have forced Samsung to put something in the newer ICS software to control the problem that some had with the saturation being too bright. I really hope someone else notices so it can be taken seriously and someone will give it some attention and fix it.
cool, yea I read that... LoL, I felt bad for you.
I think I may have found the possible culprit, if devs are doing this on purpose at least.
http://forum.xda-developers.com/showthread.php?t=1541180
I'll look at this tomorrow and see if I can brighten up my new favorite rom, team perfection (the june 28th or whatever latest rc1 version is).
PS: I killed my flash of that rom by accident this afternoon and now am reinstalling the whole damned thing and all of my apps again. all in an effort to brighten up the display. {stupid}
cheers
Don
---------- Post added at 04:29 PM ---------- Previous post was at 04:24 PM ----------
side note:
in my attempt (and final success) to download apkmanager/apktool, I came across ******* (an ad website - edit: "adf .ly" without the space). I've hit it before too.
It is very unsual for me to get so angry with a website developer that I get violently negative feelings of aggression toward them, but in this case I can strongly and confidently say that the developers of ******* need to be forcefully removed from existence. or at least their crap advertising code does.
as you were, gentlemen.
now I'm off to start hacking away at the brightness framework apk.
Cheers
Don
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
sjwoo said:
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
Click to expand...
Click to collapse
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
jsgraphicart said:
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
Click to expand...
Click to collapse
Yeah, way too sensitive. Damn, maybe it's just my Droid X2. I'd scroll up an down and it was just super sensitive, moving up and down at the slightest touch.
- Sung
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
I haven't noticed any screen flicker, or too sensitive touch
It has seemed less sensitive, to me
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
sjwoo said:
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
Click to expand...
Click to collapse
Thasian483 said:
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
You guys need to understand that this ROM will never be perfect. Even the next update will have issues.
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Thasian483 said:
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
I wasn't aware of the Motorola situation when I purchased the DX2, but quickly found out. I came from the Samsung world (Fascinate) as my last device and it seemed custom ROM's were very easy. With the DX2 it has been anything but easy. But for now really happy with the device overall and the CM10 ROM will make it great. The primary reason for my move back to CM7 was a call issue that seems to be well documented. If it isn't corrected with the new version of CM10 I will make adjustments and stick with it. Also the DX2 community here on XDA is great.
I haven't had the any call issues, but I make/receive very few calls
mostly texts and emails
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
Hey there -- just wanted to also say that I hope I wasn't coming off as a complainer (which probably meant I was!). I'm totally and absolutely grateful for all of dragonkiller's work on porting CM. I HATED my Droid X2 with BLUR -- and it has been a great joy to use since I switched to CM7.2.
I do wonder, though, that Jellybean requires a more powerful processor? CM10, outside of the sensitivity issue, felt slower in every way. I just may keep CM7.2 on this phone forever -- it's just a great ROM.
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
GoClifGo05 said:
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
Click to expand...
Click to collapse
Actually upgraded from CM7 to CM10 first time. Since moving back to CM7, I did an SBF with a clean install of CM10 and things are MUCH BETTER. Not going back at this point. This is only day two, but things are good. I did figure out that when I installed an app that CM10 did not like the screen started acting strange, but getting rid of the app and rebooting solved the issue.
I did end up with one strange problem, still working on it. I used Titanium to restore most of my apps, but wanted to do a clean install on Flash Player. So went in found the apk from my file mgr, selected "install", went to what I call the Android Install screen with two buttons at the bottom (Cancel & Install), tried to select the Install, nothing happened. I do have "Unknown Sources" checked in Security. I have tried other apk's just to test and none seem to work. Tried to move the apk's to the SD0 card, and that had no effect either. The strange thing, I had Flash Player working before going back to CM7.
I recently flashed my Samsung Fascinate with PowerWashed Team's PWGB Version 2.0 (Beta 3). I'm terribly new to using custom ROMs, but I'm quite pleased with the results. I've only had one concern with this ROM regarding the back light on the soft keys. They light up every time I touch my screen or press a hard key.
I've attempted to find a setting for this in the OS and in CwM Voodoo Lagfix Recovery v2.5.1.x screen, but wasn't able to find such a setting (Again, I'm very green so it could be right under my nose and I simply don't know it.)
I also attempted to install myriad apps to keep the back light off on screen touch including:
Screen Filter (No effect)
Night Mode (No effect)
Light Flow Lite - LED Control (No effect)
Light Manager - LED Settings (This app actually stops the back light from coming on, however it's unpredictable and works >15% of the time)
I've also done a lot of searching on the matter. I've seen where others have stated the problem, but none where there was a solution or enough information for me to further investigate a way to fix this. It's also been complicated to find information due to a variety of search terms (soft keys, led, etc.) yielding results about the camera or other things that are unrelated to my issue coupled with my lack of direct knowledge on the matter.
I'd really appreciate any advice on either directly fixing this or a source of information so I may learn more from what is causing this behavior and fixing it myself. Thanks, everyone for all the time and effort you've put in for making things like this accessible to individuals like me. I can't tell you how much I appreciate it.
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Click to expand...
Click to collapse
Thanks for the information! Unfortunately, the ROM I flashed has a stock kernel and doesn't offer this option. So, I suppose that's the first thing I need to address, but now I know where the problem lies! Thank you so much for your time and input, I'll put it to good use.
Are you saying the back lights light up even if you just touch the screen? That's strange, they only have ever lit up for me when I actually touch a soft key or hit the power button to wake the phone up.
Well good luck, I'm not sure what kernel is best for GB as I started flashing custom roms during ICS and I'm now on Jelly Bean and never going backwards.
Crawshayi said:
Are you saying the back lights light up even if you just touch the screen?
Click to expand...
Click to collapse
Yes, exactly this. It is really odd and very bothersome when trying to read at night. Even if I use the volume rocker to turn the page the lights will come on. It's maddening. I'm currently looking at the kgb kernel, but I think the nstools led option isn't actually going to address this quirk. (Directly, I believe I will end up disabling the led altogether)
If you don't mind, what rom did you choose?(Ignore, I was on mobile and did not see your signature at the time)
How has the performance been? I'm interested in doing the same, but was afraid my fascinate wouldn't handle jb very well.
Well needless to say it's different for everybody when it comes to roms, sometimes your phone will have no problem running a certain rom where as someone else's might not even boot. As for myself I've been pretty fortunate and have been able to try any rom I've wanted to with success, and I'll give you a few of my thoughts on it.
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Anyway, as far as roms go, if you're most concerned with stability and reliability then I would highly suggest CM10 (whatever the latest nightly version is). Of all the roms I've tried, it's by far the one that's given me the least hassle. That said, I'm quite fond of the tweaks offered in AOKP, mainly the voltage settings (for battery life) and the fact that it seems to vibe much better with Devil kernel than CM10 does. I've been running my current rom/kernel for a couple of weeks now, and I'm happy enough with how it's running to keep it as my daily driver for a while.
This isn't to say the GB roms aren't any good, because of course they are, but considering how nice JB roms run on our phone you'd be doing a disservice by not at least giving them a shot.
Crawshayi said:
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Click to expand...
Click to collapse
You sold me on the idea of JB. Flashed it today, and I love it so far. Plus, my soft key lights aren't constantly on! Win-win.
Thank you so much for the guidance. Your input helped turn a satisfactory experience with ROMs into a trully positive one.
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Crawshayi said:
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Click to expand...
Click to collapse
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
olalaelaine said:
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
Click to expand...
Click to collapse
Regarding the key back light, since you are on aokp jellybean now if you still want to tweak the settings, goto settings and then device settings. There you can adjust the timeout on them
Crawshayi said:
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
Click to expand...
Click to collapse
just a little hint: NEVER RESTORE SYSTEM APPS WITH TITANIUM YOU WILL GET BOOTLOOP
Sent from my SCH-I500 using Tapatalk 2
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Crawshayi said:
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Click to expand...
Click to collapse
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Crawshayi said:
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Click to expand...
Click to collapse
Are you trying too teach him too restore system apps lol?
Sent from my SCH-I500 using Tapatalk 2
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Crawshayi said:
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Click to expand...
Click to collapse
I know but it would surprise you I've had people complain because they flashed a i9000 ROM and it didn't work because the developer is stupid LOL
Sent from my SCH-I500 using Tapatalk 2
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
KanjiMan1977 said:
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
Click to expand...
Click to collapse
Went from 4.1.2 to 4.2.2 and was shocked by the phablet UI and the loss of usefull screen. That's when i unlocked my bootloader.
Been using PACMAN nightlies and am currently testing AOKP. Both are working just fine but you lack stamina mode and some sony features like doubletap wakeup and the remote.
The Android 4.3 ROMs are both very usable for everyday usage though. PACMAN comes with more additional stuff but i don't need even half of it wich is why i test AOKP right now. All i want is the tablet UI and the fast 4.3 performance.
I flashed so many ROMS lately that it is probably due to that fact and i need to wipe it clean and start from scratch. :laugh:
My wish would be a modified Sony 4.2.2 ROM with tablet UI. I think the additions Sony implemented are useful without bloating the operating system. Sadly it is completely useless with the phablet UI.
KanjiMan1977 said:
Hey people... I myself own a 312 model and love the thing to pieces. The first thing i did was get my precious root.
Right now I am reading up on the ROM releases and just dont know if I want to continue modifying or to wait.
I own a galaxy note... so i know all about flashing different roms... but my experience is usually the same with every rom.
Day one... yay... it works flawless. Day two... runs ok... then by the time a week goes by the thing just reboots so often that i get pissed off and flash something else.
So my question is what rom/kernel are people using... how long have you been using it... and how stable has it been?
Click to expand...
Click to collapse
I'm using the PAC nightly builds and having no problems :good:
As Jequan mentions, you do loose some of the stock functionality. The only bit I miss is the double tap to wake - that was nice.
The main reason I use PAC is for Pie functionality. For me, permanent on-screen navigation buttons are a waste of screen space - so I use ROMs with Pie (PA on my phone, PAC on my tablet z).
Note : If you are going to unlock your bootloader, backup the TA partition first. (Google: 'Sony DRM TA partition backup' for more info)
At the moment, the Sony stock 4.1.2 is the best ROM. Full functionality, rock stable, no annoying phablet UI.
Only problem is WiFi connection is sometimes a bit unstable. You have to test whether that's a problem for you (for me it's not, with my router it works very good).
Well Im really just waiting to see if they screw up 4.3 cause its supposed to be out really soon. Ir remote... dont care about cause there are other apps on play... just wont be as pretty. What I really wanna hold on to lol... my gallery widget... I cant find one even close to it. but if I want it that bad theres an Advanced Xperia launcher I can install. I have all the files needed to get the ball rolling. Im just still kicking myself for upgrading to 4.2.2. Now I guess either downgrade or Rom either way next step for me is a recovery cause im not flashing nothing without one. PAC was a pretty good Rom ported to the Galaxy Note... But it crashed a lot on me.. But that was back awhile ago. I like my per app dpi and all the customization bells an whistles.
Another thing I was thinking was trying the Xposed framework on the stock Sony firmwares. With the right modules it just might do the trick. But I would still want to run a recovery before trying that aswell.
After benevolently testing new phablet-ui for some weeks, I found it most inappropriate for a 10.1" device on which I work in horizontal screen orientation. So I changed to latest PACMAN ROM nightly and now after a week I can conclude, this step has payed off. Although some things do not work (yet) in this ROM, it runs very smooth, not a single reboot from the start. It has tons of options to set and play with and it brought back the tablet-ui. I did no great feature testing, only daily work with Dolphin, Firefox, Chrome, K9, Jota, FileManager HD, QuickPic, c4Droid, AdobeReader, YouTube etc. Also battery live seems to be all right to me. The only thing is I had to change to Nova launcher, built-in Trebuchet did not handle wallpaper setting properly. On the downside I lost the unique features and apps of stock ROM, but I did not use them anyway ...
What i miss, is the stamina mode, MHL hdmi, USB Mass Storage.
I use CM10.2
USB mass storage also doesn't work??
You can't connect a USB stick to the tablet, even not with Stickmount or a similar helper app??
USB Storage seemed to work for me when i had PACMAN installed.
The complete lack of deepsleep resulting in battery drain when inactive is what made me go back to Sony 4.1.2.
Once they found a way to do something like staminamode i will switch back.
All it would take is to let the tablet enter deepsleep i think.
Pacman (or any other AOSP based ROM) doesn't have deep sleep? Can't believe that!
I'm sure you just had some app which held the tablet awake.
hasenbein1966 said:
Pacman (or any other AOSP based ROM) doesn't have deep sleep? Can't believe that!
I'm sure you just had some app which held the tablet awake.
Click to expand...
Click to collapse
I reinstalled it clean just for that. Also installed greenify and disabled everything possible. Then installed wakelock detector and nope it never went to deepsleep. Neither did the AOKP ROM for that matter.
I posted it in various threads but so far i got not a single confirmation that others get deepsleep.
OK, so no deepsleep -> worse battery life?
I'm on PAC for two weeks now, I'm using the device exactly the same way as with Sony stock and activated stamina-mode. And there seems to be not much difference, maybe few percent advantage for Sony stock.
PAC Wi-Fi settings 'Keep Wi-Fi on during sleep' I set to never, but sometimes incoming mails are received anyway.
qshoo said:
OK, so no deepsleep -> worse battery life?
I'm on PAC for two weeks now, I'm using the device exactly the same way as with Sony stock and activated stamina-mode. And there seems to be not much difference, maybe few percent advantage for Sony stock.
PAC Wi-Fi settings 'Keep Wi-Fi on during sleep' I set to never, but sometimes incoming mails are received anyway.
Click to expand...
Click to collapse
When i used AOKP or PACMAN i lost about 1% battery per hour when in standby. With the sony ROM i wont lost a single % over 12 hours. I also had massive battery usage shown for "Android system". I never could narrow down why or what causes it. With timescape the display is using most of the juice as it should be.
That is why i started looking into where the juice goes and it showed that it never goes into deepsleep and no app was active.
Maybe i did something wrong i dunno.
I'm on cm and loving it. I like the simplicity of cm while still having that AOSP feel.
I'm running AOKP nightlies, only because CM 10.2 doesn't seem to have a tablet UI - I'd love to be proven wrong on this though! AOKP is pretty solid, but it has some oddities to it that make me miss CM 10.2 or stock Sony. Mostly I miss Double Tap to Wake.
AOKP is not updated very frequently either, and there are some issues that I think should be fixed that just haven't been after weeks, so I'm somewhat disappointed for now.
joe.cole1 said:
I'm running AOKP nightlies, only because CM 10.2 doesn't seem to have a tablet UI - I'd love to be proven wrong on this though! AOKP is pretty solid, but it has some oddities to it that make me miss CM 10.2 or stock Sony. Mostly I miss Double Tap to Wake.
AOKP is not updated very frequently either, and there are some issues that I think should be fixed that just haven't been after weeks, so I'm somewhat disappointed for now.
Click to expand...
Click to collapse
See that's what i dont get... all these roms running off the same buggy cyanogen but know one fixes them... they just copy them over to such and such rom and its no better cause it has the same bugs. I guess its just the fact is whether or not all the fancy dancy features is worth loosing some functionality over a stock rom. I was thinking that modified xperia launcher was great to use on stock rom (but what happened to that... been months since update) along with a couple other customization apps. I don't see to much happening in the XTZ scene I cant even find a functional recovery that works like it should... correct me if Im wrong. Almost all the threads are full of out dated info ("that was soo last week" ) or empty promises, Or is it that there are people working on new great things and keeping it hush hush. Im no dev i would learn if i knew where to start (I know starting with XML would help) but how about an update on your projects once in a while like how things are going.
But to be honest I think im gonna downgrade cause Im sick of lookin at the stupid phablet UI with its grey bars (BAD SONY).
[ROM][10/11][CM10.2][Linaro][O3][MeowKernel][TWRP][Fidelity]CM10.2 - Fidelity Edition
http://forum.xda-developers.com/showthread.php?t=2383800
Works beautifully well. Was getting boot loops on pac rom on my wifi only 32g xperiabtablet z.
I also posted in thread how to get viper4android to work and have scipts Supercharger V6 supercharged 100% working along with crossbreader.
Unrelated, is anyone else concerned about the usb port breaking on the device? im reading reports that it eventually falls off. Anyone here have their tablet since May, no issues? im buying a charging cradle to mitigate damage.
Also I really like the GUI in this ROM. I have deleted stock along launcher using no bloat,;I use Nova, way better and I locked nova in portrait mode because looks way nicer. I also flashed a swipe asop black keyboard with swipe and installed exposed module with app settings. I use greenify to grrenify all and keep a greenify shortcut on my desktop. I deleted all email apps including gmail because I use aqua mail.
Running very smooth here. Really love the expanded desktop feature, I use it while I'm gaming.
This tablet is far more superior with boot loader unlocked. Glad I did it!