yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] pio_masaki:
Why go back to 2.06? I just ran the RUU and unlocked with my token, s-off remains. Maybe in lucky since I got all that done before the update so I have the htcdev token, I'm not sure if that's an option on the updates.

I actually have to run that thing like every week now, I'm seriously sick of this phone's crap.

Tapatalked from my HTC DNA
[HTC Droid DNA] -DroidIsDNA-:
Ah, I waited twenty minutes and it stuck...I'm really hungover so I'm not my usual self with slapping roms and kernels from a new tree on my phone hahaha
[HTC Droid DNA] pio_masaki:
Hey it was out last night while you were getting to the point of being hungover, your excuse is nullified! Could have flashed it then just did something stupid and it'd be good when you got back :beer:

Tapatalked from my HTC DNA
[HTC Droid DNA] -DroidIsDNA-:
Lol I'm really getting into it now. The data roaming bug is annoying, but that's not your fault. Carbon, in and of itself, rocks man! Thanks for the update(s)
[HTC Droid DNA] orangechoochoo:
I flashed chameleon and it skipped the activation screen and went right to wifi setup as usual. All the network settings are as they should be from the start so whatever you did with Chameleon's stock settings is perfect. Maybe the buildprop needs to be changed?
[HTC Droid DNA] pio_masaki:
For CDMA I take it? They should be the same but I'll double check it tonight, there may be something in the mk files for cdma that differs between mokee and carbon and chaos.

Tapatalked from my HTC DNA
[HTC Droid DNA] kformeck:
Thanks a lot for this advice. I just had the chance to do it and worked perfectly. This new version of this ROM is great, once I got it activated I haven't had a single issue. I'm not sure about the camera auto-focus or speaker volume since I don't use these features nor do I really care about them. Great work man, the new features jammed into this version of Carbon are awesome!
[HTC Droid DNA] orangechoochoo:
Yes, the cdma version.
[HTC Droid DNA] pio_masaki:
Still no issues to speak of here, did you use the correct kernel? The newer kernel and older kernels only work with newer ROMs and older ROMs. Namely any kernel from the 6th and newer requires ROMs built on the 6th or newer.

Oops wrong pic lol

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] -DroidIsDNA-:
Clear any kernel apps data you're using. it sgould work fine
[HTC Droid DNA] Benny879:
Where would I go to clear kernel data? Originally I cleared all cache partitions but that was all. I'm definitely on the correct versions.
[HTC Droid DNA] pio_masaki:
He means reset whatever you use to change kernel settings to default or disable its settings on boot, or clear or remove any scripts, etc. Let it boot clear.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] Benny879:
Got it working with your guys advice...greatly appreciated. Thanks for the build pio. Are you on Twitter by chance?
[HTC Droid DNA] pio_masaki:
Yeah. I'm pretty boring though :p I think its by my name but in suppose tapatalk doesn't show that.. [MENTION=378530]piom[/MENTION]asaki

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] -DroidIsDNA-:
Yay!!

This update/ROM makes me hot for teacher guyz...
[HTC Droid DNA] Farva0412:
How are you guys on battery use. ?
[HTC Droid DNA] -DroidIsDNA-:
Best ROM for battery. Throw on some build prop tweaks too ;)
[HTC Droid DNA] Tsoflyyup:
Just flashed the rom are u guys running kernel with the rom or cpalmers for best batt life

---------- Post added at 08:02 PM ---------- Previous post was at 07:37 PM ----------

Anyone have an issue with the rom when using googlw hangouts? Im not receiving messages but i can send hmmmmm
[HTC Droid DNA] pio_masaki:
Crpalmers will give better battery in most cases.

Is it installed in system or data? Seems if its installed in system it does that, hangouts is still buggy IMO.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] jbarcus81:
Another great build!!
[HTC Droid DNA] Farva0412:
How can I do build props
[HTC Droid DNA] -DroidIsDNA-:
Easy, write in lines in /system/build prop and search for battery save build prop or WiFi build prop and there are tons of options.

Here, I'll make it easy for you. These work well for this ROM/ICS. No reboots or other problems. Make sure you don't repeat lines.

ro.ril.disable.power.collapse=0

pm.sleep_mode=1

debug.performance.tuning=1

debug.composition.type=hw

debug.sf.hw=1

persist.android.strictmode=0

persist.sys.use_dithering=1

persist.sys.ui.hw=true

persist.sys.purgeable_assets=1

ro.com.google.networklocation=0

ro.kernel.android.checkjni=0

ro.config.nocheckin=1

ro.vold.umsdirtyratio=20

dalvik.vm.checkjni=false

dalvik.vm.execution-mode=int:jit

video.accelerate.hw=1

windowsmgr.max_events_per_sec=240

profiler.force_disable_err_rpt=1

profiler.force_disable_ulog=1

wifi.supplicant_scan_interval=(insert whatever time here without parenthesis)
[HTC Droid DNA] pio_masaki:
Half of those are already handled in the ROM, and that maxwindow events is just way to high, 190 is the absolute highest possibly used by the system, 120 is maybe more like it considering 60fps max framerate.

Researching that stuff shows a lot is either outdated and not needed or don't really do anything or are already happening in the system. Experiment with them and see what works or not, just blindly throwing lines from pre froyo may even be detrimental to performance.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] -DroidIsDNA-:
I wouldn't have known they were handled since I don't build ROMs. If I had time I'd love to :) thanks for the info. They are ICS, but maybe I'll cut down to just WiFi scanning and power collapse. Fun to try out though!
[HTC Droid DNA] 123421342:
I tried this rom last night and had two major problems: After a full wipe of everything (both times because I tried twice) the ROM booted but I had a roaming only signal ( I flashed the cdma version), no data, and little problems like the settings to notifications swipe animation getting stuck in the middle or not being able to press the switch button in the top right corner. Second, flashing crpalmers newest kernel caused a failure to boot. Any ideas?
[HTC Droid DNA] pio_masaki:
Did you set the phone to use CDMA/lte? First I've heard of it doing that with the signal. Maybe see if the previous build does it, if you want to.

I have no idea what you're talking about form your next problem. Swiping from the status bar? I'll admit I don't do it very often, maybe once or twice a day, but I haven't had one get stuck there before.

Edit: maybe a screenshot would help.me understand what you're talking about.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] 123421342:
Yeah I tried CDMA/lte only. I will try again maybe it was a bad download. You know how you can swipe left to right to go from notifications to quick settings? If I don't fully swipe it will get stuck between animations instead of completing it. And there is an icon on the top left that serves the same function but it didnt work. Is crpalmers latest (6/8) kernel supposed to work with this because it stopped the rom from booting.
[HTC Droid DNA] pio_masaki:
Does it get stuck often? It doesn't shift over swiping for mW, but I slammed the button 30 times and it didn't get stuck. I sat here and counted.

I think I have a screen shot of me showing the kernel does run on this ROM in the last few pages, I'm on it now, but some have reported the same issue, dunno what to say about that yet, no one has provided any logs.

Tapatalked from my HTC DNA - Carbon
[HTC Droid DNA] jamiethemorris:
I'm confused about the camera, does it not focus at all or does it just not autofocus? I'm using a different ROM (cyanfox), my camera does not focus at all.
[HTC Droid DNA] orangechoochoo:
On objects farther than a couple feet it doesn't autofocus nor does touch to focus work.

It looks like focus and the amp are the only remaining bugs with CM and any rom based off of it :good:
[HTC Droid DNA] jamiethemorris:
Yeah it's definitely come a long way. I don't know if it counts as a bug but I've noticed performance could use some improvement too. Overall it's smoother than any sense or 4.2.2 ROM, but it gets really choppy playing some games and browsing in chrome, for me at least. The benchmarks show it too, although no aosp ROM will ever match the performance of the stock ROM on any phone I'm hoping we can at least get it to where 4.2.2 was. Not something that's at the top of by priority list though. I still haven't figured out my random reboots either :( but that's not the devs' fault. Crpalmer has been very helpful to me though in helping figure it out.
[HTC Droid DNA] orangechoochoo:
I don't use Chrome, but otherwise i have not seen any hints of stuttering; in fact it's very responsive. I noticed that the benchmarks are lower but that is meaningless if I can't perceive any performance drop.

Sense roms for some reason benchmark higher than CM roms but the Sense roms are not as responsive and stutters more often than not. Last week I used one of the popular Sense 5 roms fo several days and it stuttered and was not very responsive, however the benchmarks were high which is meaningless.

Since you've had a bunch of random reboots you should just start fresh and ruu.
[HTC Droid DNA] techinv:
Any other inputs from anybody on the volume of the speaker?

I have the (now) previous build of this and had to use the navigation app for a 4 hour drive last weekend that I had never done before. By the end of it, I (and my wife) were so frustrated with jumping to turn the car stereo down every time that the app announced directions.
[HTC Droid DNA] jamiethemorris:
Unfortunately I did the ruu about 2 weeks ago and it didn't help. I think it's either an app or a hardware issue. I'm still waiting for it to do a random reboot on me so i can get another last_kmsg but of course now that I want it to it's decided to be stable lol
[HTC Droid DNA] pio_masaki:
It's louder in some cases, the same in others. I consider it no better then before. Even song to song will be louder or not in the same app, and the same songs aren't always louder. At least, that's the reports I can see, mine just crackles and sounds like its underwater all the time, I've heard only backwards progress on audio since the previous build, but I think something is very wrong with mine so I can't really judge audio fixes anymore.

That said, you probably shouldn't rely on a beta ROM if you need it to work for something specific, like navigation for 4 hours without testing it for working with that purpose first, if you need reliability in all cases, stock or modded stock would certainly be the wiser choice. AOSP based ROMs just aren't there yet and are under constant development, what works in one build may be horribly broken the next, so you shouldn't consider any one thing reliable on them at this point, even booting can be hit or miss between builds.

If you hate sense, then I suggest the GPE ROM, its my fallback if something on AOSP is broken that I need, its vanilla and boring as all hell, but it works.

[MENTION=4982657]orangechoochoo[/MENTION] I checked the cdma portions of the ROMs and they appear to be the exact same, build props are the same concerning CDMA aspects, CDMA APN setup is the same, no variations, MoKee does have a section for their Chinese carriers, but that's it, I didn't see anything that would make an obvious difference right away.
[HTC Droid DNA] orangechoochoo:
Be sure not to restore apps or data, that tends to cause funky things too.
[HTC Droid DNA] jamiethemorris:
That is one thing that I always do is restore apps and data. Do you always install everything from scratch when you flash a new ROM or do you just mean if I'm having problems I should do that?
[HTC Droid DNA] -DroidIsDNA-:
I used titanium backup and I was fine. Just don't restore play store or gmail, etc. Be smart about it and usually it works. That's why the app costs $6.58.
[HTC Droid DNA] pio_masaki:
I've said it a hundred times before (not to you or here, just in general) that if you have any issues with a ROM, always, I mean ALWAYS wipe completely clean, reflash it, then test for the issue BEFORE adding apps in, or restoring anything, if you NEED to have certain apps available in the time it takes to test, like for you since its random, download fresh from the play store and see if the problem persists. As I have yet to ever see 4.3 reboot on it's own, I'm inclined to suspect an app or its data isn't jiving with the system, or a mod of some sort is in place.

Does it suck to have to redo everything and sign back in? Yup, but in the course of doing so you'll find the culprit, unless it happens to update along the way and you may never know which did it because the update may have fixed it.

So what I do when I have random issues no one else has is:

Factory rest, manually, I wipe cache, data, dalvik, system, sometimes twice.

Flash the ROM zip

Flash the Gapps

Flash nothing else, I then reboot and let the system get to the welcome screen, then I put the phone down and walk away for 10 minutes.

Come back, set everything up, sign into my accounts, and make sure to NOT leave the restore option checked.

After its set up, I leave it alone for another 10 minutes, then come back and reboot

I then test for the issue, if it remains, then its likely a ROM issue, or maybe kernel, who knows, without logs, if it's gone, I then proceed to restoring essential apps and data only, so maybe like 10 apps, no system apps, just user apps and data, then reboot, and test for the issue again, if it has yet to reappear in the usual timely manner, I begin restoring apps I can live without, but do tend to use, and their data. Again, no system apps, only user and data, then reboot, and test again. So on and so on.

If in the course of restoring apps I find the issue again, it's been narrowed down from 140 apps to within 10, from there it's easy to just factory reset it, and restore that batch of apps again one at a time.

Hugely time consuming, but its really the ONLY way to find an app causing issues in the ROM. If you're wondering, no I don't talk out of my ass, this is the exact process I follow while building ROMs and running into problems. I have a few things I add to my ROMs along the way, like filesystem mods, which won't directly cause any ROM problems, but is still left out of the mix while testing, anything that changes anything about the installation from anyone else is removed from the equation, even build.prop mods, flashable mods, anything.
[HTC Droid DNA] orangechoochoo:
I always start from scratch. Many people's problems have been traced back to restoring apps and/or data.

Try again without restoring anything and let us know if you still have problems.
[HTC Droid DNA] jamiethemorris:
I'm going to so that next time I have a reboot. Just want to be able to get one more last_kmsg first. [MENTION=4630655]pio_masaki[/MENTION] thanks for your detailed explanation, that was very helpful. I really only NEED chrome, tapatalk, Facebook, and a few others. I guess I'll run like that for a while.

One question though, sometimes the reboot will only happen once a week, should I see if it persists after 2 weeks and then restore the rest of my apps, do one at a time every few days, or install from scratch all at once after the system appears to be stable?
[HTC Droid DNA] orangechoochoo:
What has Chris been saying about your reboots and the contents of your last_kmsg?

If I were you I would just start fresh now, you and Chris may just be chasing ghosts if you continue using your rom in its current state since your problem is most likely not kernel related.
[HTC Droid DNA] jamiethemorris:
Yeah, you're probably right. As far as the last_kmsg, it was corrupted so I was waiting to get another. I'm just gonna start fresh tomorrow.
[HTC Droid DNA] pio_masaki:
Updated builds available for CDMA and GSM builds.

Nothing new device side, purely source update from Carbon.

Untested, so reports are welcome.
[HTC Droid DNA] -DroidIsDNA-:
I dirty flashed over 9/14 and everything works fine bud.

---------- Post added at 01:00 AM ---------- Previous post was at 12:53 AM ----------

I'm currently unable to send texts. I'll try clean flashing.
[HTC Droid DNA] MyNarwhalBacon:
Having issues getting CDMA Verizon data and voice to work. Tried changing Network Mode and CDMA subscription.
[HTC Droid DNA] orangechoochoo:
Also change System Select to Automatic instead of Home.
[HTC Droid DNA] phoenx06:
Sorry if this has been covered before (search was not helpful), but how can I get the green messaging icon back?
[HTC Droid DNA] MyNarwhalBacon:
Hmm I've tried that as well...
[HTC Droid DNA] orangechoochoo:
So right now what are your three settings?
[HTC Droid DNA] MyNarwhalBacon:
LTE/CDMA/EVDO Automatic and I've switched between the subscription modes a couple times. I've also tired global mode but that didn't work either.

Also clean flash.
[HTC Droid DNA] orangechoochoo:
Subscription mode must be RUIM/SIM. Then reboot.
[HTC Droid DNA] MyNarwhalBacon:
Hmm I've done that as well, I've just noticed that it seems to be defaulting back into NV... Which could be my problem... I've tried re-downloading it. Still same issue. I have the same issue on the MoKee rom as well as the 9/14 builds. No issues with the old 8/29 build.
[HTC Droid DNA] coachcrey:
Try doing a clean wipe booting. Before going through the activation pull down your status bar move over to quick settings. Toggle into airplane mode once your in it toggle out. Let your phone get connected then wolla your connected to Verizon.
[HTC Droid DNA] MyNarwhalBacon:
Ha that seemed to do it. Thanks! An interesting method that I never thought would work!

Well it worked for the MoKee rom... Still having issues with Carbon.
[HTC Droid DNA] orangechoochoo:
We should put this info in the OP.
[HTC Droid DNA] MyNarwhalBacon:
That only works with Mokee. Sadly.
[HTC Droid DNA] orangechoochoo:
I thought you're running Carbon?
[HTC Droid DNA] MyNarwhalBacon:
I am trying to. I downloaded pio's other rom MoKee for debugging purposes.
[HTC Droid DNA] -DroidIsDNA-:
You can't get to the quick settings via the notification bar when you're in setup...
[HTC Droid DNA] MyNarwhalBacon:
You can if you don't flash Gapps.

I GOT IT TO WORK!!! Airplane mode seemed to help if it wasn't for [MENTION=3826565]coachcrey[/MENTION], I would never have gotten it to.

Instructions:

1. Install Carbon DO NOT INSTALL GAPPS.

2. Head to Settings, then Mobile Networks.

3. While in Mobile networks, Enable Airplane mode via quick settings.

4. Now make sure these are checked:

[*]Data Enabled: OFF

[*]Network Mode: CDMA+LTE/EVDO

[*]System Select: Automatic

[*]CDMA Subscription: RUIM/SIM

4. Back out, then Reboot

5. Turn off airplane mode

6. Turn on data.

7. Wait 2 minutes. It should work.

8. Install Gapps
[HTC Droid DNA] pio_masaki:
What messaging icon?

Tapatalked from my HTC DNA
[HTC Droid DNA] phoenx06:
The default messaging app. I figured out it only changes colors to blue when in Dark Carbon mode. I was hoping for it to stay green like it is normally.
[HTC Droid DNA] pio_masaki:
Well that wouldn't be dark now, would it? :p you can try to use the one from MoKee, it doesn't have a dark option and wouldn't be affected by that switch.

Tapatalked from my HTC DNA
[HTC Droid DNA] coachcrey:
I Dont run Monkee it should work with carbon as well that's what I did

Also I installed the gapps and Palmers kernel with the ROM I've never had to change any of the network settings just the one time toggling into and out of airplane mode. Once my phone gains 4g I go through the initial set up.
[HTC Droid DNA] RBThompsonV:
HOLY CRAP!!! This should be in the OP... I lost the ability to use my phone for nearly a day and a half... even flashed back to stock rooted rom... Whatever was added into the new carbon for our DNA phones on Verizon CRIPPLES it!

This, however, fixed it for me.

Talk about a little bit of a heart attack (FYI, spent nearly 4 hours on the phone with verizon thinking my phone ate its sim card.. got a new one... jumped through hoops... I actually think a new one is on its way... :) )
[HTC Droid DNA] jbarcus81:
I'm late to the party here pio.. but is this the new base Carbon was working on?? I'm guessing so.. just wanted to ask my man!! Ain't forgot about ya either.. (I'll get to ya, no worries!!)
[HTC Droid DNA] pio_masaki:
This IS in the OPs. Has been for a couple of hours since it was posted. Remember there's more then 1 post you should read through, there's 3.

Edit

http://xdaforums.com/showthread.php?p=42222334

Bugs section, something that you should have visited before flashing IMO.

Tapatalked from my HTC DNA
[HTC Droid DNA] coachcrey:
I'm glad I could help you guys getting data working with Verizon.
[HTC Droid DNA] MyNarwhalBacon:
Yeah I didn't think the Airplane mode would help. It's kind of interesting that the MoKee is so easy to get working but Carbon isn't .
[HTC Droid DNA] coachcrey:
Not trying to clog the thread. I only used Monkee very early in pio's development of it. I have never had a problem with the method I said using Carbon. This is my dd I always do a complete wipe before installing x3 and I never restore apps. I am glad to help where I can. Thanks for the ROM pio!!!
[HTC Droid DNA] pio_masaki:
Update:

Updated Carbon source

Restored and fixed QCOM keystore (thanks to [MENTION=3857343]crpalmer[/MENTION] for pointing out the vendor tree changed locations)

No other changes or updates

For those with CDMA problems, please see the link at the end of post #3, end of the FAQS section, right under where it says BUGS, and the link will put you to a post that clearly walks you through getting CDMA going. I'm not sure whats going on, it's only recently started and I haven't made any changes on the device side since it didn't do it to when it was reported to be happening on a widespread basis. Without logs I can't even guess what's happening, I use the GSM builds.

RANT

Please remember this is a development thread, with an in-progress development ROM, if you can't handle the ROM possibly making your phone less then usable for your standards, please read about any issues (this includes reading at least the last few pages of the thread for recent issues) before you flash. Posting I crippled your phone will make me want to slap you with a trout, its a risk YOU take on YOUR device that things may not work when flashed from the development section of XDA. I apologize if things didn't go well, but there are certain things I can't test, and builds I simply do not have time to test, I don't intentionally release anything in a broken or non functional state, but it does and will happen, please keep this in mind, I'm not part of team carbon, I'm not a developer, I don't get paid for this, and I don't know what I'm doing, if that scares you (it should) then maybe staying on a different ROM is a better choice for you. Users tend to forget that things can and will break constantly, and these ROMs weren't built by professionals being paid for this, it's people who enjoy doing it and letting other users enjoy it, so please refrain from making comments about damaging your device for your usage.

And BTW, one more message about damages they want to be paid for will see me leave XDA forever.

Now, I'm going back under the radar again, there's been a death in the family (this morning, and for that sender, I got notified like 2 minutes before your demands for a new phone) and I really, really, don't have time for that kind of BS. I'm updating Carbon, MoKee and ChaOS with the keystore fixes over the next couple days, after that, it's up in the air if I continue or not. I'll continue to try to support users as much as I can, but this is putting us thousands of dollars into debt, I mean I have to beg for the 30 bucks for my phone, imagine how much damage 10 grand will do to us.

Lesson: get life insurance, royally screwing your family with debt amounts reserved for vehicle purchases is not a good way to go out.

/RANT

TL;DNR

Updated keystore and carbon source. Stop asking me for damages or I walk away. Mother dead this morning. Massive amounts of debt incurred. MoKee and ChaOS being updated tomorrow or next day with keystore corrections. My son thinks the carpet is lava, and I am the lava tickle monster.