Related
I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
chicmagnet2k4 said:
I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
Click to expand...
Click to collapse
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
jws3 said:
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
Click to expand...
Click to collapse
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
chicmagnet2k4 said:
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
Click to expand...
Click to collapse
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
larsuck said:
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
There is a lot of truth in what you say. ROMs on their own are usually ok; its the combination of software and install methods that leads to problems. The thing is no matter how hard you shout people always assume that its the ROM or the cook.
Case in point; I have been using Kin0kins ROMs for a little while now whilst I wait for Schaps to produce his killer ROM with the 21st century interface. K's roms are rock solid stable and fast and yet I had an instability problem after the last install.
Going through the painfull routine of "forensic investigation" of my install I discovered two things:
- I had inadvertently loaded up some software onto the SD card which had known instability problems if installed in this way. Once sorted, hey presto, one issue solved.
- 2nd issue was caused by a similar install but using software that was polled on a regular basis. Once the device went into hibernate mode it crashed, simply because the card could not wake up quickly enough to handle the software request.
Loading up old versions of software incompatible with WM6 is another popular one that tends to cause issues. Bottom line is there just is no substitute for rigour and research prior to software installs to ensure the good operation of a rom with the benefit of stability.
WB
larsuck said:
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
That is somewhat true but isnt all of my arguement I am a new member here and felt overwhelm when trying to look for a nice stable fast rom to flash and I thought about what made it hard for me. Which was there are tons of un needed comments so its like you have to go through 77 pages trying to see what this rom is about. Its overwhelming and crazy, if my way isnt all the way complete or just a bit too much it would be great for someone to think of a way to make it easier for a newbie or just people in general.
Hey,
I've just realized NFSFAN and NagROM are to different ROMs. My phone is currently on NFSFAN v16. Can someone advise which one is better for each carrier or differences between them?
BTW thanks a lot to NFSFAN, Nagrom Nniuq and everyone else for their effort/support on getting us a wm6.5 solution for our Vogue
Even though this has been discussed repeatedly....
NFS's ROM's are of the more stable variety, using tried and true Windows 6.5 builds. In addition he cooks in a long list of useful apps, tweaks, ports and theme. His next release(V17) will be his last Windows 6.5 release, when he will move onto 6.5.1 beta releases.
NagROM is coming from a different direction, his goal is to build ROM's with the newest hottest leaked 6.5.1 ROM's. His ROM's are going to need a lot more tweaking and problem solving than NFSFAN's polished 6.5 releases. From what I have gathered NagROM makes quality ROM's, but you have to be willing work around the large changes Microsoft is making with every new release. That is to say with every new release there seems to be an issue that you have to work around. Lastly NagROM's ROM's are made in a true barebones version and a slightly modified version with a few core apps added along with the new Touch Flo interface.
I have been running NFSFAN ROM's with very few issues for a while now. I have also been eagerly keeping tabs on NagROM's builds waiting for Microsoft to make a 6.5.1 build that is polished enough for me to use daily(although there are plenty of people who do use those ROM's daily).
The carrier and ROM's have nothing to do with each other, you don't have to pick which ROM by the carrier, all are fully supported.
slow88lx said:
Even though this has been discussed repeatedly....
NFS's ROM's are of the more stable variety, using tried and true Windows 6.5 builds. In addition he cooks in a long list of useful apps, tweaks, ports and theme. His next release(V17) will be his last Windows 6.5 release, when he will move onto 6.5.1 beta releases.
NagROM is coming from a different direction, his goal is to build ROM's with the newest hottest leaked 6.5.1 ROM's. His ROM's are going to need a lot more tweaking and problem solving than NFSFAN's polished 6.5 releases. From what I have gathered NagROM makes quality ROM's, but you have to be willing work around the large changes Microsoft is making with every new release. That is to say with every new release there seems to be an issue that you have to work around. Lastly NagROM's ROM's are made in a true barebones version and a slightly modified version with a few core apps added along with the new Touch Flo interface.
I have been running NFSFAN ROM's with very few issues for a while now. I have also been eagerly keeping tabs on NagROM's builds waiting for Microsoft to make a 6.5.1 build that is polished enough for me to use daily(although there are plenty of people who do use those ROM's daily).
The carrier and ROM's have nothing to do with each other, you don't have to pick which ROM by the carrier, all are fully supported.
Click to expand...
Click to collapse
well said, basically if you want the very latest build Nag is the way to go, if you can settle for an older but more stable build then NFS.
I go back and forth between both of their roms, and you cant go wrong with either one really.
NFSFAN without a glimpse of a doubt
nfsfan because it seems to do everything i need and then some, on top of that its a definite stable ROM, being im not real good with phones i dont wanna have to worry bout random issues popping up, and anything that ever happens with his ROM is usually addressed within a day or 2 and its very minor
I had NFSfans and it's solid. For some reason my phone doesn't like it. It would randomly lock me out of the phone. The old Windows Mobile Lock screen would come up and when I tried to enter my Password it would not register the button presses. So the only way out was to Take the battery out or soft reset. Both options would hard reset the phone including the memory card if I left it in. (Yes I tried flashing back to Stock about 5 times, hard reset in the new ROM a few times and YES IT REALLY DID CLEAR THE MEM CARD)
Also I thought my company changed something in their server because I could'nt get Outlook exchange to work. Turns out the ROM was the issue. I've switched to Nagrom because I was tired of the random lock-ups. I wasn't expecting Outlook to work because like I said I thought it was my company. Well with Nagrom Outlook Exhchange works just as well as it did in WM6.1. NFSFans Rom is more pretty but in my current experience NAGROM seems the most stable.
wud_e said:
I had NFSfans and it's solid. For some reason my phone doesn't like it. It would randomly lock me out of the phone. The old Windows Mobile Lock screen would come up and when I tried to enter my Password it would not register the button presses. So the only way out was to Take the battery out or soft reset. Both options would hard reset the phone including the memory card if I left it in. (Yes I tried flashing back to Stock about 5 times, hard reset in the new ROM a few times and YES IT REALLY DID CLEAR THE MEM CARD)
Also I thought my company changed something in their server because I could'nt get Outlook exchange to work. Turns out the ROM was the issue. I've switched to Nagrom because I was tired of the random lock-ups. I wasn't expecting Outlook to work because like I said I thought it was my company. Well with Nagrom Outlook Exhchange works just as well as it did in WM6.1. NFSFans Rom is more pretty but in my current experience NAGROM seems the most stable.
Click to expand...
Click to collapse
The instructions for Flashing one of NFSFAN's custom ROMS from the Chef himself:
1. Flash from BOOTLOADER mode only, let all customizations run.
2. Hard reset, let all customizations run.
There are users who suggest the "triple flash technique", In another forum NFSFAN himself suggested to a user to flash back to stock first, I think it started from there.
Question is......did you at least follow the chef's instructions?
The only tiime I have ever experienced a random hard reset with a ROM from NFSFAN is when I purposely flashed from active sync and did not hard reset after. One single improper flash. I was able to replicate most of the problems alot of users were reporting......and worse after the self hard reset. My exchange wouldn't sync contacts was one of them.
Following the above procedure (once again.....NFSFAN recommends bootloader mode himself) I have NEVER had a random hard reset, and my exchange works perfect. There was one 6.1 ROM version that had exchange issues (a beta build), but NFSFAN resolved it and I've never seen those problems since.
I can't remember the technical reason NFSFAN gave once for bootloader mode. BUT, it is his own kitchen and his ROM, therefor when he gives instruvtions on hoe to install it I do just that.
Please don't take this as a rant or anything personal. I would be interestred to hear if you flashed according to NFSFAN's instructions, and if not if you tried again and tested your exchange etc.
Cheers and happy flashing (With NFSFAN, VIN, NAG etc we have lots of that to do!!!)
were you really that bored?
right now am using NagROM because of 6.5.1 i llikkee it
wud_e said:
I had NFSfans and it's solid. For some reason my phone doesn't like it. It would randomly lock me out of the phone. The old Windows Mobile Lock screen would come up and when I tried to enter my Password it would not register the button presses. So the only way out was to Take the battery out or soft reset. Both options would hard reset the phone including the memory card if I left it in. (Yes I tried flashing back to Stock about 5 times, hard reset in the new ROM a few times and YES IT REALLY DID CLEAR THE MEM CARD)
Also I thought my company changed something in their server because I could'nt get Outlook exchange to work. Turns out the ROM was the issue. I've switched to Nagrom because I was tired of the random lock-ups. I wasn't expecting Outlook to work because like I said I thought it was my company. Well with Nagrom Outlook Exhchange works just as well as it did in WM6.1. NFSFans Rom is more pretty but in my current experience NAGROM seems the most stable.
Click to expand...
Click to collapse
It's a problem with the Windows Default Lock. Change to Windows Classic. Been a week without issues and mine was locking every day or 2.
slow88lx said:
Even though this has been discussed repeatedly....
NFS's ROM's are of the more stable variety, using tried and true Windows 6.5 builds. In addition he cooks in a long list of useful apps, tweaks, ports and theme. His next release(V17) will be his last Windows 6.5 release, when he will move onto 6.5.1 beta releases.
NagROM is coming from a different direction, his goal is to build ROM's with the newest hottest leaked 6.5.1 ROM's. His ROM's are going to need a lot more tweaking and problem solving than NFSFAN's polished 6.5 releases. From what I have gathered NagROM makes quality ROM's, but you have to be willing work around the large changes Microsoft is making with every new release. That is to say with every new release there seems to be an issue that you have to work around. Lastly NagROM's ROM's are made in a true barebones version and a slightly modified version with a few core apps added along with the new Touch Flo interface.
I have been running NFSFAN ROM's with very few issues for a while now. I have also been eagerly keeping tabs on NagROM's builds waiting for Microsoft to make a 6.5.1 build that is polished enough for me to use daily(although there are plenty of people who do use those ROM's daily).
The carrier and ROM's have nothing to do with each other, you don't have to pick which ROM by the carrier, all are fully supported.
Click to expand...
Click to collapse
Thanks for an excellent and accurate write up of both of our ROMs!
I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
EDIT: Since I posted this, the Evervolv ICS ROM (posted on Twitter only) has gained popularity. It was the first to bring partial camera support, and although ics-deck has since added it, it seems most new features show up in Evervolv first. OMX is also fading away into obscurity.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
EDIT: ics-deck-inc is now up to Alpha 5 as of this edit, while OMX is still at a standstill. It seems from this post that there is only 1 person working on OMX
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
EDIT: ics-deck-inc and Evervolv have far surpassed OMX. Personally,I prefer Evervolv, but I go back and forth between it and ics-deck-inc.
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
EDIT: ics-deck-inc, Evervolv, and OMX all include incredikernel.
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
EDIT: It's actually a lot simpler than that calendar fix... you just need to do this and all is well. There's also a fix for exchange calendar sync issues posted a little later in this thread
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
EDIT: It seems this is there because the developer makes ROMs for other devices as well. Inc uses can just ignore it
So most of the above comments are obsolete at this point, but you can still feel free to use this thread to discuss changes and such. There is a separate feedback thread somewhere, but (a) that's just for deck, and (b) this is more about discussion than feedback.
I can just wait
demarcmj said:
I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
Has anyone out there used both RECENTLY and have some thoughts?
Or does anyone who has only used one or the other want to agree or disagree with any of my impressions above?
Click to expand...
Click to collapse
I've only used OMX. I got hooked on it, but unfortunately just flashed back to CM7.1 today. In OMX, calendar does not sync with google. Wifi tethering works. Cam no work. Can't use phone as external storage when connect to computer. Also, the ring tones and volume controls are all messed up: phone never rang, just vibrates. When playing pandora, sound is very low, even at max setting. Headphones are not recognized. When I connected to bluetooth in the car, i could make a call and talk over the bluetooth, but pandora or other media would not play through bluetooth.
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!
I have been running ics-deck-inc since yesterday morning and here are some things I can tell you:
-Well, first off ics-deck-inc got updated a couple of days ago with loads of fixes including the camera. There are still some strange issues with the camera, but hey, it works.
-As far as incredikernel, ics-deck-inc already has it in the ROM. Therefore you don't have to flash it. There is a new incredikernel from 1/2/2012, while the one in the ROM is from December. Flash the new one if you want, but you don't have to.
-My calendar has worked without issue since I installed it. I think the issue is that calendars from Exchange and such don't sync with it.
-I think the Wimax thing is for another phone and not the incredible.
-Bluetooth works great. Syncs up with my head unit in my truck just fine. Pandora over bluetooth works great as well. The only thing is I can't get the metadata to stream to my head unit.
Hope that helps.
Well, I'll put my own experiences in now that a couple people have replied...
A couple days after posing the question, CyanogenMod decided to stop working for me (as others have noted that it tends to do after a period of time) so I decided to give some of these ICS ROMs a try since I was going to have to reflash anyway
I started with the Evervolv 2.1.0 Preview3 build posted on twitter so far [twitter.com]) because it was the first one to have camera support, which was one of the things keeping me from making the jump in the first place. The Evervolv build worked great for me. There was the occasional force close, but that is to be expected.
Then ics-deck-inc was updated to Alpha 4 yesterday to include, among other things camera support. I decided to move to deck since many people had noted that it was a bit better all-around than Evervolv. And now that it had camera support, there was no reason not to switch.
A few notes:
As awesomeo3000 pointed out, incredikernel is included. It's not the most up-to-date, but nobody has given any compelling reasons that you absolutely need the latest. (this was the case with Evervolv and OMX also)
I haven't really noticed a significant difference in battery life over my other ROMs, but that is probably because I am pretty much always around a charger so I don't really notice.
ics-deck comes with the Trebuchet (CM9) launcher, which is essentially stock ICS with some enhancements. It allows things like changing the # of homescreens, resizing any widget (stock only allows some), and other tweaks that are very useful but at the same time won't bother anyone who wants pure stock. Unfortunately, there seems to be two significant bugs in the app drawer in both the stock launcher and Trebuchet: (1) often times the next page of apps or widgets will show up in the background before you even attempt to switch pages, and (2) the launcher force closes very often when paging though the widgets. To alleviate that, I have switched to Nova Launcher which, like Trebuchet, is based on the stock ICS launcher but offers many helpful tweaks. I I still have had the occasional force close related to selecting widgets, but Nova also restores the long-press on the homescreen for widgets functionality, which can be used as another option if you experience force closes.
There are some small bugs that I have noticed here and there (like this one), but nothing really major, other than the well-known issues like calendar syncing and usb-host (see below). I also haven't yet tested a lot of things, like bluetooth for one.
My calendar syncing issues were solved by doing this: link. There was no need to replace the calender apps or anything like that. I can't speak for the Exchange Calendar syncing though. I can say that I was able to get an Exchange email account to work fine, but I don't use the calendar for that account.
As many people in the forums note, the multi-mount widget in the Android Market can be used to get usb-host support. Hopefully something will be built into the ROM in the future, but for now this should work. Alternatively, you can try what I use, the Samba Filesharing app. It's not as fast as USB, but wireless has it's own convenience advantages.
These are just some things I have noticed. There are some great features in ics-deck that I haven't even listed, and also some minor bugs. Alpha 5 is out now, only one day after Alpha 4, and I am excited to give it a try. I have to say that at this point I think they could drop the "Alpha." I think it could at the very least be considered "Beta" but that is just my opinion.
The important thing is this, anyone who is still using CM7 or any other ROM because they are waiting for an ICS ROM that is reasonably stable to use as a daily driver, I think ics-deck-inc has reached that point.
awesomeo3000 said:
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!
Click to expand...
Click to collapse
You should definitely try ics-deck (see my post above)
Does MMS work? how partially working is the camera? can u at least take pictures and video
Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.
TeeRom said:
Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.
Click to expand...
Click to collapse
Yup, I mentioned Evervolv's ROMs. I can definitely say the 8MP camera is working (video and panorama modes still aren't). I haven't tested out USB storage yet but they swear it works.
Right now Evervolv is my favorite, but they seem to go back and forth (hence both in my signature). Best to keep an eye on both (I've given up on OMX, big time)
EDIT: I have now also added Evervolv to the title of the thread.
I've tried both ICS deck and Evervolv, but neither display my exchange calendar in the calendar app, which is a showstopper for me. Unfortunate, as I likes me some sammich. Exchange syncs fine, and sync settings claims the calendar is up to date, but the calendar app says "no calendars" for the exchange account. Anyone had any luck with this or have a workaround that you like?
Exchange calendar issue fixed in Evervolv by flashing the zip from from this tweet.
There is a fix for the exchange.apk with the evervolv ics rom peview 5. I have it posted in rootzwiki. i had someone try it out and they confirmed it did work. Just look for post by apophis9283 in rootzwiki
Actually no need to install ext4 on any of them. Its not required.
Sent from my Galaxy Nexus using Tapatalk
http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.
ralph0015 said:
http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.
Click to expand...
Click to collapse
Thanks... here is the link to the actual twitter post: https://twitter.com/#!/MongooseHelix/status/160269895265828864
Direct Link to the ROM: http://t.co/btSyQQ0o (MD5 Sum e193f7bf9eb83233bff02aa40bb84fd0)
Direct Link to their new gapps: http://t.co/m3DOolG8
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
P.S. I updated the main thread to add Evervolv to the title... I didn't realize I could do that when I last updated it. (I also updated some of the text in there)
demarcmj said:
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
Click to expand...
Click to collapse
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.
"Haus" said:
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.
Click to expand...
Click to collapse
Does this one have panoramic for the camera? its probably the only thing keeping me from using any ICS at the moment (I could care less about video.. I think I've taken 4 in since I had the phone.. and I got it day 1)
Not sure, i went back to cm7 atm only because certain apps fc with ics
I couldnt stay away from the ics goodiness. Went back to evervolv preview 6. Hope these devs get these market apps compatible with ics soon
I loved Evervolv p5 but it still felt unfinished to me. Didn't have any FCs but after running MIUI for so long, I was missing the customization options. I'll probably be back soon though...
So my wife has had her iPhone 4s for about 6 months now, and it is a wonderful phone (for her) and it has had very few problems. Notice, I didn't say no problems, just a lot fewer than I have experienced with my epic. I've had the random reboots, fc errors ocasionally, and for a while (on cm9 beta 1 or 2) navigation would cash requiring a battery pull.
Problems with the iphone are glaring in some respects (files I would like to copy off the phone but can't because the file system is locked down, or having to use itunes because media monkey isn't ios5 compatible) and more subtle in others (like an app update that went awry somehow, requiring a phone shut down, uninstall, reinstall.)
So I wonder, why do we accept the somewhat buggy environment of Android over using an iphone that is as stable as it gets?
I think for me, it's just that I would rather have a bug crop up ocassionally while retaining control over my phone. Is it just me? What do you think?
Sent from my SPH-D700 using xda premium
amateurhack said:
So my wife has had her iPhone 4s for about 6 months now, and it is a wonderful phone (for her) and it has had very few problems. Notice, I didn't say no problems, just a lot fewer than I have experienced with my epic. I've had the random reboots, fc errors ocasionally, and for a while (on cm9 beta 1 or 2) navigation would cash requiring a battery pull.
Problems with the iphone are glaring in some respects (files I would like to copy off the phone but can't because the file system is locked down, or having to use itunes because media monkey isn't ios5 compatible) and more subtle in others (like an app update that went awry somehow, requiring a phone shut down, uninstall, reinstall.)
So I wonder, why do we accept the somewhat buggy environment of Android over using an iphone that is as stable as it gets?
I think for me, it's just that I would rather have a bug crop up ocassionally while retaining control over my phone. Is it just me? What do you think?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Because we build off of it and continue to build the whole theory behind Open Source (OSS). Much more customizable options, several designs of phones instead of one ugly ass brick that still is 3.7".
The idea that it brings innovation to a new level, there are so many reasons why and it continue on and on. if you don't like bugs go Stock Keep it at that.
Beta 3 has fixed the GPS issue I think from looking at their commits I think they fixed that stuff. But that's the beauty of android is you are able to fix issues your self if you have experience. The iPhone your forced to wait for fixes of things you find annoying. But if you want to be stable and clean of bugs. Go back to stock you won't have as many issues. Things are always prone for error. Nothing is flawless. The reason iOS is so "stable" is it is made for one phone. Not millions of others.
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
Beta 3 has fixed the GPS issue I think from looking at their commits I think they fixed that stuff. But that's the beauty of android is you are able to fix issues your self if you have experience. The iPhone your forced to wait for fixes of things you find annoying. But if you want to be stable and clean of bugs. Go back to stock you won't have as many issues. Things are always prone for error. Nothing is flawless. The reason iOS is so "stable" is it is made for one phone. Not millions of others.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Yes, somewhere in there the gps issues have been resolved. I have had no problems on beta 3.
Sent from my SPH-D700 using xda premium
Because we like to push the bleeding edge of tech
After all, if I wanted stability and to have "everything just work", I would just load up a fully polished 2.3 ROM and everything would "just work". Before I moved off of Legendary, I had ZERO issues, and performance that outdid stock by a long shot. I couldn't get things to fail, even with trying.
But I choose to run CM9, an option I would never have it this was like the iPhone, which brings my Epic to the leading edge of Android, thanks to the open source setup of Android
amateurhack said:
So my wife has had her iPhone 4s for about 6 months now, and it is a wonderful phone (for her) and it has had very few problems. Notice, I didn't say no problems, just a lot fewer than I have experienced with my epic. I've had the random reboots, fc errors ocasionally, and for a while (on cm9 beta 1 or 2) navigation would cash requiring a battery pull.
Problems with the iphone are glaring in some respects (files I would like to copy off the phone but can't because the file system is locked down, or having to use itunes because media monkey isn't ios5 compatible) and more subtle in others (like an app update that went awry somehow, requiring a phone shut down, uninstall, reinstall.)
So I wonder, why do we accept the somewhat buggy environment of Android over using an iphone that is as stable as it gets?
I think for me, it's just that I would rather have a bug crop up ocassionally while retaining control over my phone. Is it just me? What do you think?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Don't flash custom roms and stay with stock
sent from an epic touch phone
I hate to say it but flashing beta, alpha and custom roms is not for you if you want a "stable" rom, to be honest why not stay with stock? My opinion is i flash custom and BETTER rom than stock because they are built to fix problems in previous versions of android. iOS to me have always gave me problems. So ill stick with Android Open Source Project!
I think I was getting just as many, if not more, bugs with the stock roms as I am with cm9. I'm really happy with cm9.
I guess my question is being misinterpreted. I would prefer a little buggy-ness if it means I get to control my phone. The occasional hiccup is not a big deal to me if I can customize the way I interact with the phone. I like being able to access the entire file system and make changes as I see fit. I like having a choice for my launcher, and my on screen keyboard.
To me, those things are more important than rock-solid stability.
Apparently, most of you agree.
Sent from my SPH-D700 using xda premium
amateurhack said:
I think I was getting just as many, if not more, bugs with the stock roms as I am with cm9. I'm really happy with cm9.
I guess my question is being misinterpreted. I would prefer a little buggy-ness if it means I get to control my phone. The occasional hiccup is not a big deal to me if I can customize the way I interact with the phone. I like being able to access the entire file system and make changes as I see fit. I like having a choice for my launcher, and my on screen keyboard.
To me, those things are more important than rock-solid stability.
Apparently, most of you agree.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I couldn't thank the devs enough of how much time and effort that is being put into this phone, and to me 4.0 is MUCH better than 2.X.XX android. And the support is fantastic. Of course we all get defensive, our EPICS are well... just EPIC
As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
What is CarbonROM?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-PIE
-HALO
-Floating Application windows (long press app in recent apps list)
-Lock screen rotation is back
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
*not all features are available on the A100 tablet.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
Download the ROM
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup device as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your device in settings.
Change Log
8.01.13-B1:
initial build for experimenting, didn't boot.
8.01.13-B2:
Next try, boots, SystemUI crash makes it unusable, no nav/status bars
8.02.13:
WiFi works, SystemUI persistent crashing still makes device unsable.
8.02.13-B2:
BT, WiFi, sound all work, persistent SystemUI crashes still occuring.
8.03.13:
All works, SystemUI crash fixed, PIE crashing, battery mods missing, Torch doesn't work.
8.03.13-B2:
All works, Torch works
8.03.13-B3:
Fixed PIE crashing, fixed missing battery mods. Rom is now fully operational.
FAQS
If you didn't read the bugs list below, go down and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to use this build(s) as a base for my ROM, or I want to host/re release it in another country/forum, can I?
A. You may, but only if you send me a PM about it first. I've had a bit of trouble with people taking credit for my work, and I'm getting sick of it. I don't mind sharing and whatnot, but taking my build, adding a build.prop tweak and releasing it on another forum with no mention of my name is not acceptable. As for re releasing on another forum, you may if you just shoot me a link to the post about it, I would rather you link directly to this thread if possible. For those posting in forums of other languages (I know some users might in Russia, for example, use my ROMs) feel free to post for your native languages, and please include a link here also.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. I'm not going to write a guide, I did write one for CM9 which is 99.99% still a working guide aside from source urls for updated jellybean. Otherwise there are plenty of very well written guides on how to build ROMs, individual questions about build it can be asked here if you wish as this is a development thread.
Q. Can I use -insert kernel name here-?
A. You can probably use any kernel you want, but WiFi and such won't work. If you don't mind no WiFi feel free to use any kernel that will boot.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyo urass.zip"
Bugs:
MIC doesn't work
Camera crashes when you change resolutions
WiFi may not connect after being turned off, needing a reboot to come back up
Google Search doesn't work (no MIC)
Headset MIC also doesn't work
ROM may get stuck booting, powering off and on will have it boot again, not sure where this is coming from.
More, I'm sure.
Downloads:
Please visit http://pio-masaki.com for all my ROM builds
CARBON-JB-UNOFFICIAL-20130803-2330-a100.zip
WHOA BUNDY! This ROM is amazing! Finally some 4.2.2 action on the A100. Thanks!
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
MrCubbins said:
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
Click to expand...
Click to collapse
Actually, try a headset, or plug then unplug headphones, it works on the thrive for audio to get working properly, may work here too, they use the same audio system, drivers and libs.
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
MrCubbins said:
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
Click to expand...
Click to collapse
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
pio_masaki said:
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
Click to expand...
Click to collapse
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
MrCubbins said:
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
Click to expand...
Click to collapse
Well as I said unless it was reported (to me) I wouldn't have known. Hardslog wasn't reporting issues or fixes to me so I never knew it happened or how it was fixed.
The mic should be fixable, and yes it works on the thrive, so its likely a minor routing issue on the vangogh vs Antares or Picasso boards. Sound is my weakest point though, I always have troubles with it for some reason.
As for pie, there's options for all kinda shiz in there, just gotta go through them all and restart systemui to make them active in some cases. That bar is, I think, just decoration, though.
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
AngryManMLS said:
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
Click to expand...
Click to collapse
I'm just curious why anyone
A: uses the crappy camera on these things for anything but Skype
B: bothers changing the resolution of the already low resolution cameras
The kernel included is already modified just hasn't had the juice turned on yet. I'm not a fan of his kernel for my personal device, it never got along with it. If you venture into its settings you'll notice it has some extras in governors and io, no longer stock CM.
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
AngryManMLS said:
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
Click to expand...
Click to collapse
I think he used ezterrys kernel, why he chose to over the godmachine kernel you'll need to ask him about lol. It was a nice kernel for sure, but my a100 just didn't like it. My thrive kernels love mine but hate some others, such is electronics I guess.
I'm still testing the kernel for when the juice is turned on so its a pretty basic kernel otherwise, bit it should wake up real nice when its let loose.
Looking over the notes from several of hardslog's ROMs he's mentioned they have used godmachine kernels (or as I mistakenly called them "Linuxsociety"). No idea on the latest ROM that he's released since there's no mention. Let me know if you need to me to test any kernels here. My A100 is ready.
Well the kernel has some odd issues, for one lulzactive seems to just stay at top speed, it doesn't seem to scale at all. In the overclock enabled builds anychanges to min/max speeds will result in no deep sleep, the kernel stays awake at all times. Not sure whats causing either of those, lulzactive can be gone over but why the speed change locks the system awake I have no clue.
I really wish I knew what I was doing with kernels lol
Edit:
Vote, who thinks I should just update the linux society/god machine kernel to 4.2 and leave it at that? lol
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
AngryManMLS said:
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
Click to expand...
Click to collapse
The deep sleep issues are only on the overclock enabled kernel that I use, it shouldn't appear in the released build, it only shows up if min/max speeds are changed from stock. Scaling issues appear only in lulzactive, its defaulted to interactive so unless you change it, its scaling properly.
I'm not using the ezterry or god machine kernels, so its a problem unique to mine I think.
It uses cache or it wouldn't be booting at all, and you shouldn't back that up anyways I think twrp has some bugs no one ironed out and its causing oddness with older devices.
Oops. I thought you meant godmachine's kernel had those issues. My bad. I should read better next time. :laugh:
Also checking CYANOSAKI_FLEX_V2.0 the kernel it's using believe it or not is by ezterry. SetCPU defaults to interactive on this for me as well running at 1.5 ghz max speed, 312 mhz minimum. No idea if hardslog has done any mods/changes to the kernel however. Run perfectly fine on my A100. :good:
And you are right about cache let alone the TWRP bug. Just finished wiping and restoring my CarbonROM backup by the way. Successful swapping from 4.2.2 to 4.1.2 and back via TWRP backups.
Ugh I hate kernels, and I hate working IN them even more. But, it's coming along. It'll basically be the GM kernel all over again when I'm done lol.
So far vs the source I began with:
GPU/CPU/system speeds are tuned a little more, voltages tuned a little more
Adding in those missing governors, like Smartass and lagfree.
Converted/updated to BCMDHD from BCM4329
OC up to 1.5, UC to 216
I'm building this to include with my 4.2 builds, and I suppose I could just release a flashable version, it may even work on 4.1, who knows.