yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] tiny4579:
Might be apn related. Push apns.conf and eri.xml from the Inc's framework-res.apk into this rom. Also make sure you're using all the ril files for the Inc. Take a backup of your build in case you screw up. It looks like wifi is broken from the logcat. How about sound? I'm kind of anxious to work on it. With a nearly fully working desire build we got an easier port.
[Droid Incredible Android Development] Tribulattifather:
Okay guys. Uploaded. I know when to leave it in capable hands ;)

Let's get this working.
[Droid Incredible Android Development] zachf714:
I figure we pull the htc dialer and try to get wifi and data to work then get it out of dev mode into the normal mode
[Droid Incredible Android Development] Tribulattifather:
That's what i'd love; to get it out of dev mode at least.
[Droid Incredible Android Development] zachf714:
From the logcat can you see what is putting it there ... I think it may be dialer crashing and the signal being broken
[Droid Incredible Android Development] Tribulattifather:
That's possible. Because it says dialer crashes too many times.. near the end.
[Droid Incredible Android Development] Tribulattifather:
FIXED DIALER :D

Uploading..
[Droid Incredible Android Development] tiny4579:
What'd you do? Does it make calls or it just doesn't FC? I literally got home to start working on it. I need to upload my TWRP compatible updater-script and update-binary.
[Droid Incredible Android Development] zachf714:
Those scripts would be nice I have literally been in and out of fastboot mutiple times today and yesterday to flash twrp to move the file and then flash the rom in cwm 5.x
[Droid Incredible Android Development] Tribulattifather:
Just stopped the dialer for fc every second.

I'm uploading now; ETA is 22 Minutes. I'm at version 1_2 beta.
[Droid Incredible Android Development] tiny4579:
Both files are here.

http://d-h.st/users/tiny4579/?fld_id=15155#files

I just made a few changes to support the format and mount commands in TWRP and uploaded the update-binary that should work on this ROM. I removed the symlinking of the hosts file as there was nothing in /data for the hosts file.
[Droid Incredible Android Development] tiny4579:
Also, I noticed the following are for the wrong device, /system/usr/icu, /system/usr/idc, /system/usr/keylayout, and /system/usr/keychars.

I updated those and the touchscreen works normally.
[Droid Incredible Android Development] zachf714:
I will try that.... Did you use the cm9 base

I also bet if we pull the inc wpa_supplicant and wlan0 driver we can get wifi .. Mobile signal should not be hard to fix either
[Droid Incredible Android Development] tiny4579:
I pulled them from CM9. Bootable, touchscreen normal, no signal and wifi broken still. Not sure about Trib's build as far as touch screen.
[Droid Incredible Android Development] zachf714:
On tribs build the touch is off because of the dev mode... Is yours in dev mode too IE the dot on the screen following your finger
[Droid Incredible Android Development] tiny4579:
I just posted how I fixed it. I don't have that "dev mode issue".
[Droid Incredible Android Development] zachf714:
When tribs upload finishes im going to try the wifi
[Droid Incredible Android Development] Tribulattifather:
Just fixed the dev mode too.

uploading.

also did wpa_suplicant from bin from base,

wpa_supplicant.conf from etc/wifi from base

libwpa_client.so from lib from base
[Droid Incredible Android Development] tiny4579:
Did you integrate my recommended updater-script changes for TWRP?
[Droid Incredible Android Development] Tribulattifather:
Oh sry, I must've missed it. I'll look back and add.
[Droid Incredible Android Development] tiny4579:
Oh, the UMS app works for me.
[Droid Incredible Android Development] zachf714:
Im working on the WIFI I just realized ffrom work with linux that we need the inc dhcpcd
[Droid Incredible Android Development] tiny4579:
You mean the bin file? I don't think that's the problem.

It's not able to start up the device:

I/wpa_supplicant( 2149): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2149): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2149): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2149): wlan0: Failed to initialize driver interface
I/logwrapper( 2147): /system/bin/wpa_supplicant terminated by exit(255)
I/wpa_supplicant( 2242): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2242): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2242): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2242): wlan0: Failed to initialize driver interface
I/logwrapper( 2241): /system/bin/wpa_supplicant terminated by exit(255)
I/wpa_supplicant( 2269): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2269): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2269): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2269): wlan0: Failed to initialize driver interface
I/logwrapper( 2267): /system/bin/wpa_supplicant terminated by exit(255)

We should check with the devs of the ROM we're porting how they fixed wifi. Quicker than beating our heads. I spent way too long last time trying to figure this one out.
[Droid Incredible Android Development] zachf714:
I think I may have it I just need to flash but that would be a good idea to check with them maybe myself or trib can talk to them tonight or tomorrow

---------- Post added at 01:42 AM ---------- Previous post was at 01:17 AM ----------

alright [MENTION=3500210]tiny4579[/MENTION] [MENTION=1725519]Tribulattifather[/MENTION] I sent the devs on the desire Sense4 port a message
[Droid Incredible Android Development] tiny4579:
Thanks [MENTION=4674343]zachf714[/MENTION].
[Droid Incredible Android Development] Tribulattifather:
Just was about to do that. Glad I didn't just now; don't want to bombard em lol..

Also, ver 1.4 of the beta is uploaded.

Has everything in it that has been discussed in this board so far..
[Droid Incredible Android Development] zachf714:
Oh yeah Bluetooth is broken to but it is in the desire as well
[Droid Incredible Android Development] Notorious:
For camera try adding the Camera.smail* tree from cm10 into framework/android/hardware so you at least have Aosp camera or diff them maybe it could work?
[Droid Incredible Android Development] zachf714:
Well I have to look on the desire thread because the dev of the sense 4 we are porting from basically forked a fully working one from another desire dev so im going to look there

EDIT : I contacted the real dev of the desire sense4 just now.. Now we wait
[Droid Incredible Android Development] Tribulattifather:
Just got Sense 4.1 to boot too. I'm making another thread for it.

Kinda fun with new projects to work on at our leisure lol.
[Droid Incredible Android Development] tiny4579:
I'd kind of rather just get one working as a daily driver honestly. Sense 4 to 4.1 should be minor. I wonder if anyone will try sense 5 that's on the one.

Though porting a rom to different device and making it boot is still neat.
[Droid Incredible Android Development] tiny4579:
Why from cm10 framework if this is an ics rom?
[Droid Incredible Android Development] Notorious:
My bad forgot its ICS and not jb :p
[Droid Incredible Android Development] zachf714:
I figure a sense 5 port would take months to get working seeming the only device we can really port from right now that cdma might work is the DNA
[Droid Incredible Android Development] Tribulattifather:
Hey, guys, I just got camera working on Sense 4.1..

Can someone test and see if I fixed Data/Service too when it's uploaded in about 10 more minutes?
[Droid Incredible Android Development] zachf714:
I am about to get the wifi fix ... im actually in the middle of a conversation with greeneyes
[Droid Incredible Android Development] Tribulattifather:
Very nice. Can't wait, lol.
[Droid Incredible Android Development] zachf714:
I figure since sense 4.1 is newer and is working better we use that instead and wifi fix should be within the next few min (atleast I hope)
[Droid Incredible Android Development] Tribulattifather:
I couldn't agree more.
[Droid Incredible Android Development] Kaepernick:
May as well use the best/latest working version, right?
[Droid Incredible Android Development] Tribulattifather:
Yeah, you're right, lol.

[MENTION=3500210]tiny4579[/MENTION]:

Is your latest JB 4.1.2 Rom this one:

cm-10-20130118-TINY-inc.zip from here?
[Droid Incredible Android Development] zachf714:
are you trying to base the 4.1 version on jellybean .. the desire 4.1 is still ics ... We should stay there for now I think
[Droid Incredible Android Development] Kaepernick:
Agreed. Maybe it's best to get the ICS version working before considering Jelly Bean if the version on Desire is the only one you have to work with.
[Droid Incredible Android Development] Tribulattifather:
Oh, no, I'm just asking a question about another project I have in mind. I probably should have asked that here. My bad, lol.
[Droid Incredible Android Development] Kaepernick:
Ah, okay, was a bit confused there, heh. I'm going on limited info, since I haven't been looking into this deeply, so I probably shouldn't even be commenting right now. I'm just glad the Dinc is getting some extra love, despite its growing age. :good:
[Droid Incredible Android Development] zachf714:
dont tell me its sense 5 lol
[Droid Incredible Android Development] Kaepernick:
Nothing wrong with trying. :p lol
[Droid Incredible Android Development] Tribulattifather:
Lol, yes; that's it.

But, I can't work on it until about 6 more hours until my daughter goes to bed.

Then i'll be free all night.
[Droid Incredible Android Development] zachf714:
Yah know every time I go to fix something you have another port LOL :)
[Droid Incredible Android Development] zachf714:
Hey [MENTION=3500210]tiny4579[/MENTION] can you look in the kernel for wlan0 ... I think the problem may be that it isnt in the kernel
[Droid Incredible Android Development] Kaepernick:
So, just to clarify, are you guys going to be working on Sense 4 or 4.1?
[Droid Incredible Android Development] Tribulattifather:
Well, tbh, I'm gonna work on sense 4.1 first.

Then I'll use Sense 4.1 to fix Sense 4.
[Droid Incredible Android Development] zachf714:
No wifi yet so far I have gotten no where

What we need is the name of the wifi drivers/files
[Droid Incredible Android Development] tiny4579:
Are you sure? The wlan0 part last time I worked on sense 4 was in all the necessary files in the ramdisk and rom. Check build.prop and related wifi files in ramdisk and wpa_supplicant.conf and the dhcpcd conf files. If it's fine there, the wifi module isn't interfacing with the supplicant libhardware_legacy.so properly.

What did the desire devs say?
[Droid Incredible Android Development] zachf714:
It may be the kernel is what I think but I think it may be the libhardware_legacy so I can just pull that from the cm9 ... All the desire dev said was to look in his updater-script for the files which I did not find, but if you would like I can upload it. Also im booted into windows right now how can I check the ramdisk .. I also checked the dhcpcd and wpa_supplicant and they seem to be fine
[Droid Incredible Android Development] Tribulattifather:
Wooot, the wife is home early so I can start developing now :D

Okay. Let's get this WiFi working. And tbh, I think that if we figure one out we'll be able to figure out what's wrong in sense 4.1 as well.
[Droid Incredible Android Development] zachf714:
HAHA I need to finish my HW then I can put some more time into this

---------- Post added at 12:39 AM ---------- Previous post was at 12:00 AM ----------

I figured I would tell you guys that the WIFI problem is comming from libhardware_legacy.so

EDIT Actually I think it was that the buil.prop was not point to the ril

EDIT AGAIN - Nope still no wlan0 error
[Droid Incredible Android Development] Tribulattifather:
I was researching and it can either be eth0 or wlan0.

I'm trying eth0 everywhere now. But I don't think that will work because eth seems too familiar to ethernet..
[Droid Incredible Android Development] zachf714:
Im trying to edit the libhardware_legacy.so right now to fix the wifi problems in it then maybe it will work

The Problem is most definitlly the libhardware_legacy.so and we cant just edit it so can you look at it and try I need to go to sleep
[Droid Incredible Android Development] tiny4579:
What tells you that it's the reason? Is it because I suggested it?

I could have told you you can't view the file normally.
[Droid Incredible Android Development] zachf714:
The pieces that can be read specifically say the error in the logcat and the WiFi drivers it trys to load are wrong from what can be read

---------- Post added at 02:30 AM ---------- Previous post was at 02:19 AM ----------

I figure two ways to do this ... Either find a way to edit it or make copys of the incs identical drivers and name them what they are named in the libhardware_legacy.so
[Droid Incredible Android Development] Tribulattifather:
Edit: Meant for sense 4.1
[Droid Incredible Android Development] zachf714:
Alright cool... I have an idea with wifi.... What does the Logcat say now
[Droid Incredible Android Development] Tribulattifather:
I'm flashing a test now.

I'll take a logcat after.

But the upload will be done in 3 minutes, so i'll bet you could get to it faster than I could lol.
[Droid Incredible Android Development] zachf714:
I gotta go to sleep.. I think I wake up earlier than you lol 5:45 am est
[Droid Incredible Android Development] Tribulattifather:
I gotta get up at 6:45 est. In NY.

Kid gets on bus at 7:41.

Then relax and dev time :D well until 2:41, lol.

(laid-off atm)

Back on topic. The test failed with wifi for sense 4.1 so flashing the ver 1.3 for sense 4.1 and then i'll pop a logcat on the other thread.
[Droid Incredible Android Development] tiny4579:
It might be better to get this one fully up and running than to try to mess with the slow Sense 4.1 ROM. I think I'll release a 2.0 version of the Sense 4.1 ROM and switch over to this one once I can get a copy of this ROM.
[Droid Incredible Android Development] tiny4579:
Dev-host is back up. I'm downloading it now. I tried to fix WiFi on the old Sense 4 LUXE ROM by PureMotive but was unsuccessful after several hours trying to fix it. The WiFi fix from Sense 4.1 didn't seem to work on that ROM. It's a shame as that ROM does fly and runs smoothly.
[Droid Incredible Android Development] Vernox701:
That does suck ....any chances you tried the boot.img from 4.1
[Droid Incredible Android Development] tiny4579:
The boot.img won't work as is. I have another idea today that I might try if I can't get wifi on the TribulattiFather Sense 4 ROM.
[Droid Incredible Android Development] tiny4579:
Who's got LUXE working with WiFi? Yep, I do. Now to figure out camera and audio (hopefully in and out of calls) and we have a daily driver.

I ended up using the boot.img from 4.1 and used the init.rc that was originally in LUXE along with applying the same WiFi fix for 4.1.
[Droid Incredible Android Development] zachf714:
Cool that's neat I remember it being fast

---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------

I will ask trib about audio and camera
[Droid Incredible Android Development] tiny4579:
I already PMed him about audio and camera. I got camera to load but it force closes so I'm making progress.

Update: Now camera loads without force closing but due to no mounting sdcard within the phone, it can't take pictures.
[Droid Incredible Android Development] zachf714:
Oh OK.. Can you upload progress so i can take a look at sdcard mounting
[Droid Incredible Android Development] tiny4579:
Just fixed emmc mounting using the vold.fstab and /system/bin/vold from Trib's sense 4.1 ROM. No FC errors but it doesn't take pictures still.

This is the error:

E/QcomCamera( 2381): CameraHAL_CopyBuffers_Hw: MSMFB_BLIT failed = 22 Invalid argument
[Droid Incredible Android Development] zachf714:
Try these and see if it fixes the External http://d-h.st/myfiles?fld_id=17150#files
[Droid Incredible Android Development] tiny4579:
I was actually wrong. Both internal and external mount but I think in sense emmc needs to be primary. And your link tries to go to your directory's root which I can't hit.

The error before is a preview error and doesn't seem to be the reason why pictures aren't getting taken.
[Droid Incredible Android Development] zachf714:
Alright I will fix that

---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------

DERP
[Droid Incredible Android Development] tiny4579:
I think you missed the part where I said I fixed the mounting to phone already.
[Droid Incredible Android Development] tiny4579:
Working on a few more things and then I'll push a build in the LUXE thread.
[Droid Incredible Android Development] Tribulattifather:
Hey guys. I sold my Dinc a while back. I really miss developing with you guys.

But, the time came for me to sell my toys.

So please use any of my files from my Droid Incredible working folder as you guys see fit.

Just a friendly reminder to accreditation.

I suggest for beginner devs to compare my roms with theyre own.
[One (M7) General] h.han:
I would like to start a topic dedicated to black HTC One, since there is still not many people got the black One, and hope this topic could help others see how durable/not durable the casing is, especially over time.

We all know that both silver and black One have the same aluminum casing, anodized, difference is the colour. So silver version naturally hides the scratches but black version will show clearly the scratches.

Hope all the black One owner would come and share the condition of their phone, if it is still no scratch at all, or already developed some annoying marks.

I will start from me, I had the black One for 1.5 days, still naked no case, there is one small scratch at the bottom speaker area, very thin line so must be due to sand; top edge near headphone jack has little scratch or chip, not sure what it is, but silver colour so noticeable; the top plastic strap at the back above camera had developed a crack since got the phone.

All of them are very small so not able to show on picture, will definitely post picture if things get worse.

I will try to report back often, but hope this post won't grow too big so it would mean actually the black One is holding up pretty well. :)

+++++++++++++++++++++++++++++++++++++++++

[Update: 24/04/2013, 5 days after I had the phone, I always baby the phone.]

I got two tiny scratches, picture included, see post 12.
[One (M7) General] woodekx:
Sadly, EXACTLY why I didnt get black. I saw MANY videos on Youtube and alot of them had scratches around that shiny bezel and along the edges. They weren't even highlighting the scratches, I just noticed them. Man, it looks beautiful, but unfortunately shows many of the scratches that the silver doesn't. I remember the iPhone 5 went through the same thing.

Really sucks that people cant show off the beautiful phone without a case. I have a thin leather case on mine, and REALLY wish I could go "naked" but know better. (been there, done that!). At least I love the looks on the leather.
[One (M7) General] h.han:
Oh, that's really sad and worrying, I have seen colleague's black iPhone 5 which only had two tiny marks at the edge, so I thought One would be similar. I accept the danger of having the black, but really want to see in a normal careful usage, will it be scratched badly still?

Tomorrow Monday is a good day, I can put my phone in the bad world to see how it survives or not... Until tomorrow!
[One (M7) General] woodekx:
Just a caveat to my prev. post. ALL aluminum (encased) phones, ESPECIALLY if they are anodized to a color, will have the same issues.
[One (M7) General] h.han:
Yes I totally agree with you, however I want to see how the black One stands daily usage and if it gets scratches very easily.

I have the black One, at least in the next few days I will report back.

Just hope this could help other people make sensible decision on what colour to choose.
[One (M7) General] woodekx:
I really don't think the real problem is as much the anodizing, is as it is with the routed beveled edges. As beautiful as they are, those sharp edges seem to be very venerable to chips/ dings. Iphone 5s had the same issues. Hey, I love em! The really give the phone a "rich" look.
[One (M7) General] sand1303:
I can't even get a black one. That's what I'm waiting on. Only available in silver here.
[One (M7) General] Riyal:
I think the shiny part on the edges aren't anodized and is just plain paint. I haven't seen any anodized metal that's shiny my whole life lol! It should be matte texture so that maybe the reason why it's chipping. Unlike the silver though the edges are exposed plain aluminum it doesn't have any paint nor anodized layer so it won't chip.

I also wanted the black HTC One and said to myself I'll just apply a transparent nail polish on the edges but I got fed up waiting so got the silver instead and waiting for it to arrive till now.

Good luck guys! For me given the chance right now if I could choose I would still select the black over the silver.

All I could suggest is...

1. You could coat the edges with transparent films to avoid the scratches or

2. You could scrape the black color on the edges and give it a shiny silver bezel instead like the silver one. That would make it look more premium if you ask me...

Imagine it... :D Pure black matte body with shiny silver edges :)
[One (M7) General] h.han:
I am not so sure about black phone with shiny silver bezel but won't mind see one in real life (not mine though)

Just update on the condition of my black One, it's been more than 3 days since I got it, naked all the time, no new scratches or chip apart from two which appeared on day 1.

Yes I did baby my phone, not like avoid using it, just not putting other stuff in the same pocket, trying not to drop it, not touching the metal button near my pocket when putting phone in, laying it on a clean surface, etc. All commonsense.

But yes, the shiny bezel may give up first another reason being the edge of the bezel is so sharp, touching it over time may just remove the colour of the coating and show a silver line. But so far it's holding up well.

Comparing to the back, the up and bottom speaker pieces seem more easily scratched, the surface of them seem more rough than the back aluminum which means sand or other hard material will cause more obvious damage to them.

Hope other people who had the black One longer than I did can share what the condition of their phones are at.
[One (M7) General] vegetaleb:
Mmmm but where are the pics??
[One (M7) General] h.han:
I only have two very tiny scratches they are too small to be captured on camera, apart from those two, my phone is in new condition.

Hence no picture sorry.

I would like this thread to gather conditions of as many black One as possible to give a real life example of what to expect if anyone wants to get a black One. Or if you don't have the black One, anticipation of what could get scratched/chipped easily is also welcome.
[One (M7) General] h.han:
Ok, on the way home on the train, just saw a light mark dot on the edge of top frame above the front camera. Did not do anything special to my phone, was browsing web...

Will update a picture later when a reach a camera.

It's very small but big enough to be noticed.

[UPDATE] picture uploaded
[One (M7) General] Riyal:
Hi again guys! I am gathering info with regards to the chipping info of these phones... I just wanna ask... Where does the scratches/chipping happen?

Is it on the unibody aluminum part of the phone or within the speaker grills? I'm not sure yet but I'm thinking maybe the speaker grills aren't anodized.