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

Root [ROM][4.1.2]AWE Inspired Moonshine White/Ginger V2.9a Final[Works with stock device]

sorry for the noob question, but this is just a rom made to look like kitkat, but not an actual rom based on 4.4 kitkat? the original just had 4.1, but the 'themed' part in the description makes me think its just 4.1 made to look like kitkat.

edit: after further reading it appears this one is based off of the one dragonhart6505 made: http://androidforums.com/awe-all-things-root/824562-rom-kernel-awesome-rom-v1-1-released.html

U are correct it is still 4.1.2 base themed to look like kitkat, this rom is me and starkravings creation and is not based off of awesomerom
 
uploadfromtaptalk1398461711264.jpg
New dialer coming along...:D
 
Love the ROM guys. Really brings back life to my phone and gets rid of all that VM garbage. Few questions. First off in the wizard it paused and wanted me to insert a sim card. The AWE does not use a sim. Was not a issue, I just skipped it and never seen anything about it again. Secondly am I able to use the rb3 kernel with this to allow over clocking or am I stuck with stock? If I can use a kernel what is the preferred performance settings for rb3 or is any reasonable settings safe to use? Finally I would like to know If the glitches with TrevE have been addressed. When I was on stock I used the most recent TrevE, however, when I was finished using it I had to reboot my phone to get it to stop broadcasting. This is not a deal breaker for me to keep using your ROM. Just a inconvenience.

Thanks for your time. Look forward to seeing how far this ROM will go.
 
Love the ROM guys. Really brings b life to my phone and gets rid of all that VM garbage. Few questions. First off in the wizard it paused and wanted me to insert a sim card. The AWE does not use a sim. Was not a issue, I just skipped it and never seen anything about it again. Secondly am I able to use the rb3 kernel with this to allow over clocking or am I stuck with stock? If I can use a kernel what is the preferred performance settings for rb3 or is any reasonable settings safe too use? Finally I would like to know If the glitches with TrevE have been addressed. When I was on stock I used the most recent TrevE, however, when I was finished using it I had to reboot my phone to get it to stop broadcasting. This is not a deal breaker for me to keep using your ROM. Just a inconvenience.

Thanks for your time. Look forward to seeing how far this ROM will go.

The tethering itself causes the inconvenience not the ROM. I have had to reboot every phone I've used it on. I don't know about using the custom kernel but I've heard its unstable with this ROM. And the SIM issue in the wizard can b ignored and ull never see it again until an update for this ROM becomes available and ull only see it in the setup wizard
 
Love the ROM guys. Really brings back life to my phone and gets rid of all that VM garbage. Few questions. First off in the wizard it paused and wanted me to insert a sim card. The AWE does not use a sim. Was not a issue, I just skipped it and never seen anything about it again. Secondly am I able to use the rb3 kernel with this to allow over clocking or am I stuck with stock? If I can use a kernel what is the preferred performance settings for rb3 or is any reasonable settings safe to use? Finally I would like to know If the glitches with TrevE have been addressed. When I was on stock I used the most recent TrevE, however, when I was finished using it I had to reboot my phone to get it to stop broadcasting. This is not a deal breaker for me to keep using your ROM. Just a inconvenience.

Thanks for your time. Look forward to seeing how far this ROM will go.

You'd have to use awesome ROMs kernel. Extract and flash awesome ROMs boot IMG. It works perfectly
 
What's that kernels default clock speed.

It uses the rb3 kernel I believe which clocks out to 1.9 at max without boot loop or crash but usually I just set it to a max of 1.5 with smartassv2 and deadline.

Side note: I noticed something with the lock screen today. It has options to unlock to camera or Google now. However when I select those options it does nothing. I have to then go to the unlock to go to those. Shouldn't it immediately unlock to those without having to swipe a second time to unlock? Once again not a major issue just an inconvenience.
 
It uses the rb3 kernel I believe which clocks out to 1.9 at max without boot loop or crash but usually I just set it to a max of 1.5 with smartassv2 and deadline.

Side note: I noticed something with the lock screen today. It has options to unlock to camera or Google now. However when I select those options it does nothing. I have to then go to the unlock to go to those. Shouldn't it immediately unlock to those without having to swipe a second time to unlock? Once again not a major issue just an inconvenience.

I have noticed the lockscreen issue only with gel, all other launchers i have used seem fine
 
I have noticed the lockscreen issue only with gel, all other launchers i have used seem fine

Yeah I am using gel. I don't want to switch to another launcher as this perfectly mimics KitKat with only adding pages as you want not having several by default and I love the fact I can swipe right to open Google now. I guess I will just live with it then. Thanks for replying so quickly.
 
I'm using gel and I haven't had this problem. The shortcuts work just fine for me. Strange.

So when you select Google or the camera it immediately opens to these without having to swipe to the unlock? That is strange. I wonder what you did differently then me to get this result.
 
It uses the rb3 kernel I believe which clocks out to 1.9 at max without boot loop or crash but usually I just set it to a max of 1.5 with smartassv2 and deadline.

No it's different, it only clocks to 1.8xx ....also he's asking about what the defaulted speed is, not the max.
 
Back
Top Bottom