yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] zachf714:
We are porting from the desire and the N1 is closely related to both that is why I think it may be the ramdisk but I said something about the ramdisk yesterday or the day before to
[Droid Incredible Android Development] tiny4579:
Did you check what wifi drivers they are using? Ics on the Inc still has the old broadcom drivers.
[Droid Incredible Android Development] Flagmax:
Ahhh few hours later I finally get the Dialer back! :p I think it was something to do with TWRP not wiping right. Oh and I could not find /boot or /datadata in TWRP. But I did wipe all I could dalvik, system, data and cache but I think that was not enough.

So I flashed back to cwm5020, formatted boot, system, cache, data, datadata, sd-ext, wiped dalvik and battery. Flashed 1.4 and got the dialer.

Edit: The missing Dialer reappeared with CWM so most likely it not TWRP related.
[Droid Incredible Android Development] zachf714:
i will download it and check ....... I seriously think the ramdisk is the problem but I still have no reply from the N1 dev
[Droid Incredible Android Development] tiny4579:
Ugh is this rom not fixed with TWRP? I feel behind just missing two work days and one evening.
[Droid Incredible Android Development] zachf714:
After messing around I have a new WIFI Logcat

E/WifiHW ( 194): Supplicant not running, cannot connect
E/WifiStateMachine( 194): Failed to setup control channel, restart supplicant
D/WifiHW ( 194): wifi_stop_supplicant enter
D/WifiHW ( 194): wifi_stop_supplicant end rifgt 1
D/StateMachine( 194): handleMessage: new destination call exit
D/StateMachine( 194): invokeExitMethods: SupplicantStartingState
E/WifiHW ( 128): Failed to open wlan fw path param (No such file or directory)

E/SoftapController( 128): Softap fwReload - failed: -1
E/WifiStateMachine( 194): Failed to reload STA firmware java.lang.IllegalStateE
xception: Error communicating to native daemon
W/CommandListener( 128): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 128): Setting iface cfg
E/WifiStateMachine( 194): Unable to change interface settings: java.lang.Illega
lStateException: Unable to communicate with native daemon to interface setcfg -
com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0
.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}

D/WifiHW ( 194): wifi_start_supplicant_common enter
D/NetworkManagementService( 194): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 194): flags <[down]>
D/StateMachine( 194): handleMessage: new destination call exit
D/StateMachine( 194): invokeExitMethods: DriverLoadedState
I/wpa_supplicant( 2525): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2525): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2525): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2525): wlan0: Failed to initialize driver interface
I/logwrapper( 2523): /system/bin/wpa_supplicant terminated by exit(255)

bcm4329.ko is the wifi module so it and the ramdisk seeming they are both compiled while building the kernel are the problem
[Droid Incredible Android Development] Flagmax:
Last night I was using TWRP 2.4.4.0. Did a Factory Reset and wiped Dalvik and 1.4 flashed fine with Dialer.

Today I flashed ToB rom, it seemed ok. Few hours later I repeated the procedure perhaps 5 times to get 1.4 to flash but could NOT get Dialer to show up. I also tried TWRP 2.5.0.0 with same results. I tried Wiping everything except sdcard and emmc.

It was only when going back to CWM5.0.2.0, formatting boot, system, cache, datadata, data, sd-ext, and wiping dalvik and battery that I finally saw the Dialer.

This is what I went through today. I lost trust in TWRP. I do like how nice it is and built-in file manager.

So whoever is using TWRP, we need to make sure it flashes right.

Edit: The missing Dialer reappeared with CWM so most likely it not TWRP related.

---------- Post added at 02:29 PM ---------- Previous post was at 02:03 PM ----------

Comparing logcats from TWRP and CWM I see something different.

TWRP

W/PackageParser( 213): Unknown element under <application>: uses-permission at /system/app/DialerLauncher.apk Binary XML file line #16

[B]I/PackageManager( 213): /system/app/DialerLauncher.apk changed; collecting certs[/B]

W/PackageParser( 213): Unknown element under <manifest>: HTC-SDK at /system/app/DialerLauncher.apk Binary XML file line #35

CWM

W/PackageParser( 195): Unknown element under <application>: uses-permission at /system/app/DialerLauncher.apk Binary XML file line #16

W/PackageParser( 195): Unknown element under <manifest>: HTC-SDK at /system/app/DialerLauncher.apk Binary XML file line #35

Don't know what it means but I see many " changed; collecting certs" from TWRP flash such as I/PackageManager( 213): /system/app/Phone.apk changed; collecting certs that I don't see in CWM flash.

---------- Post added at 03:26 PM ---------- Previous post was at 02:29 PM ----------

I have just repeated the test and the dialer is gone.

What I did.

Using CWM5020:

1. Format boot,system,cache,data,datadata

2. Wipe Dalvik and Battery

3. Flashed ToB 3.0

4. Reboot, all looks good with ToB rom.

4. Flashed TWRP 5200 PB31IMG.zip

5. Advanced Wipe checked everything except Sdcard and emmc

6. Flashed Trib_Incredible_Sense_4.1_v1.4.zip

7. Reboot.

I notice I had Cell Service at first then as I was going through setup I see the X. Finished, and No Dialer.

So either I am missing something or TWRP is not liking me.
[Droid Incredible Android Development] Tribulattifather:
Okay.

I've done a lot so far and I feel i'm closer.

First, I extracted the ramdisk from my boot.img in v1.4.

I edited the init.rc like it says to do so HERE.

I then rebooted and no go on wifi.

Then I found THIS. Did that. (But did not do the virtous thing. Just below the annotation at step 4.

And lastly made sure all areas where wlan0 should be were, from THIS.

I realized in the build.prop I had spaces between the '=.'

I'm flashing this 2nd test now.

I'll upload regardless if this works or not. It'll be v1.5.
[Droid Incredible Android Development] zachf714:
That should fix it .... See lol I told you guys there was a ramdisk problem
[Droid Incredible Android Development] tiny4579:
Above poster. I think you're on to something about TWRP. It works fine for pretty much every other ROM. Did you actually test TWRP on other ROM's or just this one?

I have a missing dialer but no signal with TWRP.

And Trib, about the network, I flashed my Jellybean 4.1 kernel and wlan0 shows up in busybox ifconfig -a. The following is a snippet from my logcat pertaining to wireless:

I/wpa_supplicant( 2420): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2420): Could not set interface wlan0 flags: Operation not permitted
E/wpa_supplicant( 2420): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2420): wlan0: Failed to initialize driver interface
I/logwrapper( 2418): /system/bin/wpa_supplicant terminated by exit(255)
[Droid Incredible Android Development] tiny4579:
Why do you keep bumping up the build numbers so rapidly? Just wondering. I hope it works too.
[Droid Incredible Android Development] tiny4579:
Can you really say this without any actual confirmation? I still stand by my statement that all the pieces have to match properly. It's not an issue with one particular component.
[Droid Incredible Android Development] zachf714:
My hole idea with it coming from the ramdisk is from the TF101 ... We use a mountloop kernel to dualboot linux and without the right kernel supplements and the right things in the boot.img it get the same wlan0 is not a device error
[Droid Incredible Android Development] Flagmax:
Yes I have tried TWRP with Touch of Blue v3, yours truly Tiny's CM10.1, Stock rooted OTA 4.08.605.19 710RD and Jellybean RC4 4.2. I don't recall anything weird with any of them.

If the dialer is missing in v1.4 then you got a bad flash I think due to TWRP. But I still have no idea why last night TWRP did flash correctly. Anyways, I am back on CWM5.0.2.0 now.

Edit: The missing Dialer reappeared with CWM so most likely it not TWRP related. I've reverted back to TWRP couldn't resist using touchscreen.
[Droid Incredible Android Development] tiny4579:
The init.rc isn't the problem. I've been down that whole path earlier. Also, there's a difference between "whole" and "hole".
[Droid Incredible Android Development] Tribulattifather:
Because I try things one at a time. I don't mix attempts as to minimize the confusion.

Can you send me the boot.img you just used? I'd like to see if i can edit the init.rc like what I did with this boot.img.

Also, the modules too.

Edit:

I am now attempting to add the modules from the cm9 base we used. I just used the 'bcm4329.ko' in the last v1.5 attempt.

This time I have 'bcm4329.ko' and 'ifb.ko.'
[Droid Incredible Android Development] Aca902:
You should use evervolv kernel jb (from what i saw you have support from evervolv)...so download from git, and before you compile kernel you will find in some folder of downloaded kernel config txt documents for devices evervolv supports (they are for auto compile, and sorry i didnt use android for some time and i dont remember which folder), and you will find yours... in that config you should change the configuration for compling the kernel to seperate the drivers (modules) for example wifi (bcmdhd.ko), there are choices -y -n -m (something like that i don't remember correctly, google it) for modules to seperate them. When you successfully compiled the kernel and modules (command:make modules) seperatly, you should find a appropriate boot.img (use from roms where modules are seperated) and extract it... move the kernel there.

Now the ramdisk, it binds kernel with modules... in some of these .rc files or others you will find wifi configuration, if bcm4329 the change it to bcmdhd,.... and if some of these of .rc files contains name of board of a different device, for example ueventd.mahimahi.rc (mahimahi- nexus one board) or inside of file, change it to name of the board of droid inc. Make boot.img, put in rom, and modules in /modules.

This is what i remember, sorry for my english, and i hope it helps... it helped me, i did it the same way. You could also download my rom, and try editing ramdisk from boot.img of my rom.
[Droid Incredible Android Development] zachf714:
Aca to the rescue by my request lol thank you I may try that
[Droid Incredible Android Development] Tribulattifather:
Do you think if I could upload the ramdisk, you could take a look and maybe let us know what changes should be made on the lines etc..?

Side note: v1.5 is uploaded (and btw, once we get out of BETA i'll put the version number back to 1.0).
[Droid Incredible Android Development] Tribulattifather:
Use my v1.5 if you can. As I have so much edited already.
[Droid Incredible Android Development] zachf714:
To be honest the only thing I dont know how to do is compile the kernel IE the command to start it
[Droid Incredible Android Development] tiny4579:
I have a working incredikernel with the bcmdhd.ko drivers. I'm trying a few things as I didn't see anything wrong in the build.prop from what I could tell. Interface gets set as wlan0. init.inc.rc from ramdisk also shows wlan0. Do you have special hooks in your ueventd.board.rc? I didn't mean wifi working by the way.

[MENTION=1725519]Tribulattifather[/MENTION], if possible I want incredikernel in this ROM.
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] We could do a new branch called incredisense for the kernel that is set up just for sense4/4.1

---------- Post added at 01:40 AM ---------- Previous post was at 01:35 AM ----------

I can download his rom and upload the boot.img to devhost if ya want so you dont have to download the entire thing ... So you can check it
[Droid Incredible Android Development] Tribulattifather:
Send it my way.

I'm actually in the middle of a test too in the init.inc.rc and init.rc

I'd like to try doing what I'm doing here on your kernel too.

Then I wanna test both.
[Droid Incredible Android Development] tiny4579:
if I can get it to enable wifi even manually, we're in business. Right now I'm compiling wifi as a module. I noticed the external gave a module load error in dmesg.

If I get it figured out or regardless, I was going to upload the zImage for the ramdisk and bcmdhd.ko for /system/lib/modules.
[Droid Incredible Android Development] zachf714:
[MENTION=1725519]Tribulattifather[/MENTION] Meanwhile breakout the Pink Floyd lol ..... Im looking at the modules as well but tiny will ALMOST DEFENITLY get it before me
[Droid Incredible Android Development] Flagmax:
I've just tried 1.5. It has same problems as 1.4.

Also, the Dialer did NOT show up this time and I am using CWM5020 and formatting everything. This is weird sh#t I tell you.
[Droid Incredible Android Development] tiny4579:
Uploaded zImage and wifi module to http://d-h.st/users/tiny4579/?fld_id=15155#files

I think the trick is in aca's boot.img. Still getting errors like below:

W/CommandListener( 136): Failed to retrieve HW addr for wlan0 (No such device)
E/WifiStateMachine( 201): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
E/wpa_supplicant( 2359): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2359): WEXT: Could not set interface 'wlan0' UP

If I manually load it, it tries to bring down wlan0

sh-3.2# logcat | grep wlan0
D/CommandListener( 136): Trying to bring down wlan0
E/wpa_supplicant( 2154): Could not set interface wlan0 flags: Operation not permitted
E/wpa_supplicant( 2154): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2154): wlan0: Failed to initialize driver interface
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] would you like me to download the rom and upload his boot.img to look at
[Droid Incredible Android Development] tiny4579:
I already did and am looking at it now.
[Droid Incredible Android Development] Tribulattifather:
Here's his kernel

Edit, you got to it first, but i'll leave it for future devs..
[Droid Incredible Android Development] tiny4579:
I haz working WIFI!!!!

Use the boot.img, wpa_supplicant and libhardware_legacy.so I uploaded along with the wifi module bcmdhd.ko needs to go to /system/lib/modules.

I got wpa_supplicant and libhardware_legacy.so from Aca's ROM.

http://d-h.st/users/tiny4579/?fld_id=15155#files
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] OH MA GOD lol Nice good one im going to try it now
[Droid Incredible Android Development] tiny4579:
I was right, the issue was with the path in libhardware_legacy.so. I guess switching out the path. Not sure if the other steps were necessary. I guess they were but I'm not messing with something broken. Also, I can enable bluetooth but can't seem to connect my Galaxy Nexus to my Sense 4.1 Inc. I could enable mobile data but I'm not sure if it works as I don't have service.
[Droid Incredible Android Development] Tribulattifather:
Well done. Well done.

Now onto USB hahahahaahahah.

But before that, can you point me to which file and which line you edited?

I feel like i'm missing something..
[Droid Incredible Android Development] tiny4579:
I modified the init.inc.rc in the ramdisk. Multiple lines. No time to go into detail tonight. Have you checked the storage_list.xml in framework-res.apk yet regarding USB to PC?
[Droid Incredible Android Development] Tribulattifather:
Okay. As long as I know the file i'm okay. I know what lines you're talking about.

But no, I haven't even begun the usb fix adventure yet. Possibly tomorrow. I'm going to enjoy the Rom a bit, lol.
[Droid Incredible Android Development] Tribulattifather:
[MENTION=3500210]tiny4579[/MENTION] :

Wifi error for me. Damn.

What files do you have in the lib/modules? Just the bcmdhd.ko?
[Droid Incredible Android Development] tiny4579:
Try it on 1.4. It really doesn't matter what you have there. It only loads what it's gonna load. Did you remember the wpa_suplicant and libhardware_legacy.so?
[Droid Incredible Android Development] Tribulattifather:
Okay. Cool.

Thank you.

But are you adding the .ko to what's there or replacing?
[Droid Incredible Android Development] tiny4579:
Edited post but you responded too quick.
[Droid Incredible Android Development] Tribulattifather:
I see. Flashing now.

Man, I have to say, we really are doing better than expected on this project.
[Droid Incredible Android Development] Flagmax:
You guy Rockz :good:

WiFi works here too WPA. Used 1.4 zip and changed out the 4 files, thanks tiny4579.

BT turned on but can't detect my Plantronics 510.

Mobile Network can't connect.

I can't figure out the Dialer issue. Bastard shows up when it wants. Anything I can try?

Also sometimes my lock screen looks crazy.
[Droid Incredible Android Development] Vernox701:
wifi works with 1.5 also using Tiny's method ,no data ,wifi tethering (obviously since no data) but it connects

genie widget weathers shows my location .I tried to use the locations app but it said insert sd card.

I also have fc from system ui and android.process.media

so only sound is from volume keys

Bluetooth connects to my motorola s10-hd but sound isn't working

loaded file manager gave it root permisions navigated to media sounds they only play through phone speakers or wired headsets
[Droid Incredible Android Development] Flagmax:
So I installed Root Explorer now. Anyone know what files should I rewrite to fix missing Dialer?
[Droid Incredible Android Development] Vernox701:
Htc Dialer+Crc_Vie_Eva_Enr_Pro_S40.apk it should be located in system/app folder
[Droid Incredible Android Development] Flagmax:
Thanks. I tried my best but made it worst so ended up flashing to Stock, wiping twice then flashed 1.4+wifi and Dialer is there. I don't know why I am the only one having issue with Dialer.

Tried Youtube app and Sound is heard but no Video just black screen.
[Droid Incredible Android Development] Vernox701:
Well I flashed 1.4 and guess what no dialer.
[Droid Incredible Android Development] Flagmax:
Dang bastard got you too. Well I was blaming TWRP until it happend with CWM. I really have no idea what it could be. It could be related to Wipe, permissions or how the system loads up on first boot. Sorry I am no help.
[Droid Incredible Android Development] Vernox701:
I think the rom is too big but sense may handle things differently ...THE SMART guys will have it fixed in no time.
[Droid Incredible Android Development] Flagmax:
Google Voice don't work related to AudioRecord?

I/htcfs-main(10279): ############# HTC FS - END 1 ##################
D/WifiStateMachine( 250): fetchRssiAndLinkSpeedNative RSSI = -44
D/WifiStateMachine( 250): fetchRssiAndLinkSpeedNative RSSI = -44
I/PowerManagerService-JNI( 250): [Stability] PowerManagerService_userActivity JNI pass power key event to PowerManagerService userActivity()
I/RecognitionControllerImpl( 9922): startRecognition(RecognitionParameters{session=null,request=0})
I/RecognitionControllerImpl( 9922): State change: STARTING -> STARTING
I/RecognitionControllerImpl( 9922): New mic stream.
V/AudioPolicyManagerBase( 8054): getInput() inputSource 6, samplingRate 8000, format 1, channels 10, acoustics 0
V/AudioPolicyManagerBase( 8054): getInput() failed opening input: samplingRate 8000, format 1, channels 16
E/AudioRecord( 9922): Could not get audio input for record source 6
E/AudioRecord-JNI( 9922): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java( 9922): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
I/MicrophoneInputStream( 9922): #new 0
E/RecognitionControllerImpl( 9922): Audio error
E/RecognitionControllerImpl( 9922): java.io.IOException: not open
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.endpointer.MicrophoneInputStream.<init>(MicrophoneInputStream.java)
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.speechservice.MicrophoneManagerImpl.getMicInputStream(MicrophoneManagerImpl.java)
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.speechservice.MicrophoneManagerImpl.setupMicrophone(MicrophoneManagerImpl.java)
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.speechservice.RecognitionControllerImpl.startRecognition(RecognitionControllerImpl.java)
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.speechservice.RecognitionControllerImpl.access$300(RecognitionControllerImpl.java)
E/RecognitionControllerImpl( 9922):	at com.google.android.voicesearch.speechservice.RecognitionControllerImpl$1.handleMessage(RecognitionControllerImpl.java)
E/RecognitionControllerImpl( 9922):	at android.os.Handler.dispatchMessage(Handler.java)
E/RecognitionControllerImpl( 9922):	at android.os.Looper.loop(Looper.java)
E/RecognitionControllerImpl( 9922):	at android.os.HandlerThread.run(HandlerThread.java)
E/RecognitionControllerImpl( 9922): ERROR_AUDIO
I/AudioService( 250): AudioFocus abandonAudioFocus() from android.media.AudioManager@40df2b00
[Droid Incredible Android Development] Vernox701:
Installed 1.6 having the disappearing dialer issue.tried changing permissions still not working for me..WiFi works Bluetooth connects but music only plays through wired headset or phone speakers
[Droid Incredible Android Development] Aca902:
Nice work...feel free to use anything you need from my rom :)
[Droid Incredible Android Development] tiny4579:
Any ideas on our disappearing dialer issue that happens at random?

I think we should incorporate sd-ext instead of using symlinks from /data to get more app space.
[Droid Incredible Android Development] zachf714:
If we use sd-ext can't we map that to the emmc

---------- Post added at 01:40 PM ---------- Previous post was at 01:09 PM ----------

I'm happy with the performance and battery of this .. now we need to recompile the systemui to get rid of the 3 dit overlay
[Droid Incredible Android Development] tiny4579:
Sd-ext is for sdcard. I take it you don't have an sdcard on your Inc.

Performance was poor for me even after being booted. The menu overlay is due to the one not having a menu button. Maybe pull systemui from sense 4?
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] I have one but if we could do the same thing to the 8gb emmc partition we could keep the speed because sd-cards can be slow like my class 2
[Droid Incredible Android Development] tiny4579:
It should be possible. I'd tack it on at the end of emmc. I'm not sure how capable recovery is at creating partitions though. I mean I know you can run parted from adb shell but it's not a novice task. Sd-ext functionality though is already built into recovery.
[Droid Incredible Android Development] zachf714:
The way they do it is with scripts in aroma so I guess we could do the same thing
[Droid Incredible Android Development] tiny4579:
Also I'm wondering if you had to edit libhardware_legacy.so or you pulled it from another Rom. Editing so files is difficult without a disassembler.
[Droid Incredible Android Development] Aca902:
Don't know about dialer, strange... i remember i had some problems, try dialer from my rom. I don't know how this rom installs (space related) and works, i don't own a droid inc and never did, so can't help you with this. sorry.

I didn't edit libhardware_legacy.so, i used it from another rom.
[Droid Incredible Android Development] zachf714:
Right now it symlinks ... I think the

dialer just does not like being symlinked

---------- Post added at 07:27 PM ---------- Previous post was at 07:09 PM ----------

I kind of want to look into the GPU drivers to see if I can rid the ROM of the graphical errors .. Also [MENTION=3500210]tiny4579[/MENTION] we should just be able to move the files to the internal 8gb in a folder on the root of it and just symlink it and we could do the same thing for the data partition for apps from the play store