I've been reading a lot of posts lately of people wanting to go from CM7 to stock 2.3.3. Why would someone do such a thing? Am I missing something??
Sent from my Nexus One using XDA App
Call wonks are on cm7
Sent from my Google Phone
decoyjoe said:
I've been reading a lot of posts lately of people wanting to go from CM7 to stock 2.3.3. Why would someone do such a thing? Am I missing something??
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
They don't want to use or don't know about the Dewonkificator and because of the wonks are willing to go stock. They think battery life sucks on CM7 and want better battery life with stock. They want the latest Android version. They use only RC or Stable versions of CM and therefore don't know about the improvements in the nightlies after RC1.
I would like to try stock for few days just for comparison and most likely go back to CM7 after that.
I have never heard of call wonks. What are they?
Sent from my Nexus One using XDA App
decoyjoe said:
I have never heard of call wonks. What are they?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Gremlins that inhabit the CM7 ROM. They often run amok when you make or receive calls.
I think it only affects the stock dialer though. I use CM7 for daily use and have for a while now, and have seen a wonk once. It was ugly.
Dialer One didn't have any issues to my knowledge.
I've been using the stock dialer more on CM7 then I have in the past with little to no issues, although I don't call that often.
Cyanogen is the best
Hmm when i flash an other ROM then Cyanogen it feels wrong for me.
Imo Cyanogen is for me the way how Android must looks like.
I've been thinking about buying myself a new device but then i thought: "There will be no Cyanogen on it and maybe they wouldn't support it". So i wait for the next Googlephone.
My N1 will survive another year.
Great thanks to the Cyanogen team for this great job no one make a better one!!!
where's the tutorial of CM7 to stock 2.3.3..
i want to try it.. anyone please copy the link..
Backup followed by flashing the GRI40 zip from the development forum.
Does anybody think that the G1 will get an ICS port or a CM9 port?
Sent from my iPhone 4 using Tapatalk
Wait what happen to cm8?
Sent from my HTC Magic/G1 using XDA App
Some people say that since Honeycomb wasn't open source, so there wasnt a CM8 that they might just skip over it and go to CM9
Google just released ICS source code, hopefully this will speed thing up...
I hope Ezterry or Yoshi are able to create a ICS ROM for us.
anyone tried new ICS 4.0.3 ? I`m just curious to hear some opinions
Hey guys.As I can't post in the dev section,-would it be possible to use St.Matt's ics alpha 2.1 rom using the kernel from alpha 3?Thanks
Sent from my HTC Incredible S running ICS Alpha 2.1 using XDA App
heat. said:
Hey guys.As I can't post in the dev section,-would it be possible to use St.Matt's ics alpha 2.1 rom using the kernel from alpha 3?Thanks
Sent from my HTC Incredible S running ICS Alpha 2.1 using XDA App
Click to expand...
Click to collapse
No. Won't work because of the different KGSL drivers (this is the only change anyway).
For what reason did you want to try this?
Till now pretty smooth and rock solid, hardly any fc's.
Only problem i found is the render glitch, which makes browsing and maps and gmail almost unuseable.
So if you need the features like cam and previous stated, i wouldnt recommend it. Remember its an alpha and not a beta or stable
st.matt said:
No. Won't work because of the different KGSL drivers (this is the only change anyway).
For what reason did you want to try this?
Click to expand...
Click to collapse
Was interested to try this as I much rather prefer your own aosp Alpha 2.1,rather than the cyanogen mod port.Would be nice to get hw acceleration,but nvm.
Something I am very looking forward though is the 4.0 & sense 3.5 hybrid,especially when we consider we could de-sense it and still have stable,camera working Rom.
Sent from my HTC Incredible S using XDA App
I've been using St.Matt's ICS Alpha build for a couple of weeks now and have enjoyed the ride so far.
With the latest release and the native HW acceleration, I am willing to forego the omission of a camera.
There is the rather annoying Browser rendering issue and a couple of glitches with the graphics sometimes but it works amazingly otherwise.
Sent from my Incredible S using xda premium
I think it works great it is smooth but there are some glitches. but having said that the glitches and not having the ability to use my 8mp dual flash camera..... lol, is not kind of a pain in the butt. so i will be waiting for htc to release the camera kernal so we can fix this bug and begin our journey onto the ICS platform.
This is just my person opinion some others may disagree and say that the camera bug is ok and they are willing to forgo this problem and use it anyways. Me not so much but like i said i am eagerly awaiting the fixes and cant wait to see what the amazing devs can conjure up in there magic pots lol.
hope this helped you.
I agree with the above... but it was nice to give it a test run. koodos dev team
Sent from my Incredible S using XDA App
I have asked this question before but since 2 months has passed, what is the fastest rom out right now?
Sent from my HERO200 using XDA
Would anyone care to answer my question?
Sent from my HERO200 using XDA
The one you dl and tweak out.
#Root-Hack_Mod*Always\
laie1472 said:
The one you dl and tweak out.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I meant a rom by itself. But thanks
Sent from my iPad using Tapatalk HD
Well from all the roms I've flashed the fastest ones I've dealt with is the DX OS and CM 7.2 release that just came out. I prefer DX OS but for me MMS was a big problem. I couldn't receive any through the DX messenger and had to use the default messenger to receive them. Besides that I loved it. CM 7.2 just seems a lot more stable and less of a headache if you want something simple and easy to use. Haven't had any problems so far with the OS. But at the same time I've tweaked it a lot more then any other ROM so far.
cm7.2 by far.
if your looking ics wise, i'm not trying to toot my own horn here but the aokp port i added is quite snappy, fun to mess around with. if you try it, see if youtube works! i havnt had anyone verify for me, i know it works for me though.
sense wise, definitely zero hero from matt and dastin
supercharger v6 script goes a long way with our old phones, use compcache and cut out bloat that you know you absolutely wont use
AOKP JB Pons
Goo.Im Download for Kangs
Dev-Host Mirror
(updated only on request)
MediaFire Mirror
(updated only on request)
Evervolv Gapps
(recommended due to their smaller size)
Goo.Im Gapps
Merged Commits for Jellybean
(aka Changelog)
What this ROM is:
Full version of AOKP JB using tiny's/chad's incredikernel synced and compiled from source
Uses only AOKP, and...
missing components from Evervolv
incredikernel source from tiny4579
and my HTC Incredible device tree
Now supports OTA updating via the Goo Manager app
Removed (with my suggested replacements, if any)
SuperSU (I use Superuser compiled from source instead)
Known issues:
PREFACE: I haven't tested this as extensively as CM10, so there may be hidden bugs. It's early, and I'm going for coffee.
Currently doesn't boot. Working on it to get it fixed.
Performance settings, particularly CPU, don't stick
Watching YouTube videos causes the phone to reboot flickers occasionally
Video camera has a very low fps (it stutters)
USB Tether (and the toggle for it) FC's
anymore, let me know
Source/Sauce (in case you missed it)
AOKP (I use their manifest.xml)
Evervolv (I use parts of their frameworks and other repositories to fix qsd8k specific issues)
My device tree for the Inc
Incredikernel by tiny
FAQ:
[Q] Gee, Pons, this here looks fun. How do I compile it myself?
[A]Here ya go, lil guy. Just follow these instructions: How to Compile AOKP JB for the Inc (if you encounter any issues using this to compile, please report here so I can troubleshoot and update if need be)
Why a thread? Basically, a couple of users have asked me to do this, and jellybellys hasn't pushed one out in almost two months, nor responded to his thread in even longer. I did ask him if he plans to continue support via PM, and he said yes (but is busy with a thing called life), so this is only to tide those over who like AOKP over CM10. I'll quit building them when he starts up again.
Credits/Thanks
All credit goes to Cyanogen and the rest of the CM team (who's work Team Kang borrows heavily from), and especially our HTC Incredible maintainers, as listed by the CyanogenMod site: jistone (aka CUViper/This Guy), slayher, and of course, koush. Of course, don't forget about the Evervolv team, who has given our qsd8k device a lot of love. And how could we forget Team Kang, since this is AOKP, after all
In addition, I'd like to thank Albinoman for bringing AOSP JB to the Inc first, Zimeron for bringing CM10 to the Inc first, tiny4579 for his incredikernel, and JellyBellys for bringing AOKP to the Inc first.
For some reason, I have received several requests to put a donation link in my profile. You can always donate to the CyanogenMod project or the Evervolv project or Team Kang, but if you feel you HAVE to donate to me, I've put a link in my profile, and all donations will go towards upgrading my computer, so I can stay on top of this for CM10/11/and beyond.
Lol, saw this in goo when I was seeing if you had put up a new build of CM10 before I found this thread. Nice surprise to say the least
Sent from my ADR6300 using Tapatalk 2
rickyg946 said:
Lol, saw this in goo when I was seeing if you had put up a new build of CM10 before I found this thread. Nice surprise to say the least
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
Quit cheating and use the Goo Manager app.
I switched from your CM10 to this and so far so good. Having choice is great, and this seems to be a good ROM thus far.
Thanks Pons!
rickyg946 said:
Lol, saw this in goo when I was seeing if you had put up a new build of CM10 before I found this thread. Nice surprise to say the least
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
Ive been testing since the 15th .... It runs great..... He sent me a preview build
Sent from my Transformer using Xparent Red Tapatalk 2
7he Messiah said:
I switched from your CM10 to this and so far so good. Having choice is great, and this seems to be a good ROM thus far.
Thanks Pons!
Click to expand...
Click to collapse
zachf714 said:
Ive been testing since the 15th .... It runs great..... He sent me a preview build
Sent from my Transformer using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
If anyone runs into bugs that aren't listed in the OP, (especially big ones), please let me know. If I get enough confirmations or if I can replicate it myself, I'll add it to the OP.
Also these probably won't be nightly. I'll look at how AOKP does their releases and their merges, but a tentative schedule will be I'll release when AOKP releases or if there's a lot of merges or if I fix a groundbreaking bug.
It has been running great for me; nice and responsive, stable in what I've done.
One thing that I've noticed is that for some reason, it seems that switching activities holds the possibility to cause some graphical glitches (visually similar to what we see with the camera, but on the UI). Not a big thing, and it doesn't happen every time, but I figured I'd mention it.
PonsAsinorem said:
If anyone runs into bugs that aren't listed in the OP, (especially big ones), please let me know. If I get enough confirmations or if I can replicate it myself, I'll add it to the OP.
Also these probably won't be nightly. I'll look at how AOKP does their releases and their merges, but a tentative schedule will be I'll release when AOKP releases or if there's a lot of merges or if I fix a groundbreaking bug.
Click to expand...
Click to collapse
Alright well it can be unofficial builds like their Sunday releases but UNOFFICIAL and my battery is better on AOKP than cm10
Sent from my ADR6300 using Xparent Red Tapatalk 2
I love this! Thanks Pon!
Looks like notifications have no sound for me. Tried various methods but no go. I've had quite a bit of issue with notifications being very quiet or not at all on all JB roms.
Forgot to mention otherwise it runs great.
nfiniti9 said:
Looks like notifications have no sound for me. Tried various methods but no go. I've had quite a bit of issue with notifications being very quiet or not at all on all JB roms.
Click to expand...
Click to collapse
is your profile set to silent?
Hey, Pons, loving this ROM so far. it is very smooth and responsive. Any idea why performance settings (frequency, governor, and scheduler) don't stick after a reboot? They return to default even though I enabled the set on boot toggle. Not sure if it's a bug, kernel design, or something else altogether. Thanks again.
Anyone else have this problem or any recommendations? Should I be using a third party app like SetCPU?
RokuP said:
Hey, Pons, loving this ROM so far. it is very smooth and responsive. Any idea why performance settings (frequency, governor, and scheduler) don't stick after a reboot? They return to default even though I enabled the set on boot toggle. Not sure if it's a bug, kernel design, or something else altogether. Thanks again.
Anyone else have this problem or any recommendations? Should I be using a third party app like SetCPU?
Click to expand...
Click to collapse
I have same problem
Sent from my ADR6300 using xda app-developers app
mhejek said:
I have same problem
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Yes try Setcpu... I don't have problems with it
Sent from my ADR6300 using Xparent Red Tapatalk 2
zachf714 said:
Yes try Setcpu... I don't have problems with it
Sent from my ADR6300 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
$2 well spent. Thanks!
RokuP said:
Hey, Pons, loving this ROM so far. it is very smooth and responsive. Any idea why performance settings (frequency, governor, and scheduler) don't stick after a reboot? They return to default even though I enabled the set on boot toggle. Not sure if it's a bug, kernel design, or something else altogether. Thanks again.
Anyone else have this problem or any recommendations? Should I be using a third party app like SetCPU?
Click to expand...
Click to collapse
Going to test this out, then add to bug list once I confirm. Depending on how long work takes tonight, I might or might not get a chance to fix it. It's probably a permission issue somewhere.
Edit: confirmed.
Edit edit: and updated bug list with it. Thanks for the report.
PonsAsinorem said:
Going to test this out, then add to bug list once I confirm. Depending on how long work takes tonight, I might or might not get a chance to fix it. It's probably a permission issue somewhere.
Edit: confirmed.
Click to expand...
Click to collapse
Thanks, I sure do appreciate your time, whatever the outcome... Also, just curious, is it normal for AOKP to not have a WiFi AP (hotspot) notification toggle? I found that kind of odd.
RokuP said:
Thanks, I sure do appreciate your time, whatever the outcome... Also, just curious, is it normal for AOKP to not have a WiFi AP (hotspot) toggle? I found that kind of odd.
Click to expand...
Click to collapse
Not sure. I never really used AOKP. To double check, you'd have to look at an officially supported device (with WiFi AP capabilities) and see if they have it.
PonsAsinorem said:
Going to test this out, then add to bug list once I confirm. Depending on how long work takes tonight, I might or might not get a chance to fix it. It's probably a permission issue somewhere.
Click to expand...
Click to collapse
Just tossing in my observations as well, in case it's possibly related: in my instance, the ROM Control app was unable to modify build.prop to change the DPI setting. It told me that it had, but in fact the file was untouched. I just did it with ROM Toolbox instead, but ROM Control offered me no error messages or information.
7he Messiah said:
Just tossing in my observations as well, in case it's possibly related: in my instance, the ROM Control app was unable to modify build.prop to change the DPI setting. It told me that it had, but in fact the file was untouched. I just did it with ROM Toolbox instead, but ROM Control offered me no error messages or information.
Click to expand...
Click to collapse
Did you grant rom control root
Sent from my Transformer using Xparent Red Tapatalk 2
---------- Post added at 12:45 AM ---------- Previous post was at 12:43 AM ----------
PonsAsinorem said:
If anyone runs into bugs that aren't listed in the OP, (especially big ones), please let me know. If I get enough confirmations or if I can replicate it myself, I'll add it to the OP.
Also these probably won't be nightly. I'll look at how AOKP does their releases and their merges, but a tentative schedule will be I'll release when AOKP releases or if there's a lot of merges or if I fix a groundbreaking bug.
Click to expand...
Click to collapse
How big is Live Wallpapers,,,, Would have to recompile to add it
Sent from my Transformer using Xparent Red Tapatalk 2