[ROM] [Unofficial] Evervolv 4.0.0 (Android 4.4.4 kitkat)

Search This thread

Pons

Senior Member
Sep 2, 2010
3,932
2,067

musical_chairs

Senior Member
Mar 6, 2012
1,072
1,226
Yeah, feel free to grab a logcat. I'm not sure the latest on the camera. I believe it works fine so it could be a memory issue triggered by SnapChat due to the older hardware.

The camera works, but it seems to be really slow at saving pictures, also media scanning etc. is really slow. I'm not surprised to hear that an app like snapchat is misbehaving.

While Tiny and Pons are here, I was trying to get the torch app to quit FC'ing. I can see from the log that is is crashing due to a permissions problem writing the flashlight brightness device file. Just for kicks I changed permissions on that file and the torch started working. Is this a problem in the way the device init's the flash, or a problem in the torch app? Since third-party apps and the camera can use the flash without this hack, I'm thinking the issue is the torch app.
 

musical_chairs

Senior Member
Mar 6, 2012
1,072
1,226
My guess is this. Could be the torch, but more than likely this. Check out other device's init, and compare your torch to theirs. And please don't just set it to 777.

Heh...you nailed it:
https://github.com/Evervolv/android...mmit/5289b1b73e23e040762f3647f7130c12da9b84c8
So is 666 really better than 777?

Edit: Hmm, interesting, this makes the old HTC flashlight app work, complete with its three brightness levels.
Edit #2: ...which makes sense because Sense sets it to 666. Just checked one of the decrepit dincs in my collection.
Edit #3: Okay, it's 666 in froyo but 660 in GB and everything else. Whatever.
Edit #4: ...which explains why in Froyo any app was able to use the flash at multiple brightnesses but in GB you had to be root or the HTC flashlight app. HTC must have decided that having the flashlight brightness world writeable was a bad idea, and what - made their flashlight app root?
 
Last edited:

anuragnigam

Member
Mar 12, 2012
17
0
I tried this rom. Amazing to see kitkat running on this ancient phone:thumbup:
My inputs :
Messaging app is FC-ing.
Back key is not working most of the time.
I think its very close to become a daily driver.


Sent from my ADR6300 using Tapatalk 2
 

hfl12

Senior Member
May 8, 2011
119
8
Thanks for the work.
The system is really lagging. Some apps are unresponsive/ slow to open. Sometimes, Wifi is having a hard time turning on.
 

musical_chairs

Senior Member
Mar 6, 2012
1,072
1,226
Messaging app is FC-ing.
Back key is not working most of the time.
FC's need logcats. The messaging app works here (mms's do not send or download though). Back key is fine here (except on one of my decrepit dincs but that's a hardware issue.)

The system is really lagging. Some apps are unresponsive/ slow to open. Sometimes, Wifi is having a hard time turning on.
Regarding lag, give it some time. It takes quite a while to scan media / build databases / settle / whatever you call it. Once that is done it should run mostly okay. A basic system (rom, gapps, and a handful of lightweight apps) should run at a tolerable speed.
 
  • Like
Reactions: tydiamond11

ryukiri

Senior Member
Jun 17, 2012
498
701
Yeah, feel free to grab a logcat. I'm not sure the latest on the camera. I believe it works fine so it could be a memory issue triggered by SnapChat due to the older hardware.

Alright, I'll get a logcat sometime this week. (my friend has the phone and I'll probably need to teach him how to do it)
 

musical_chairs

Senior Member
Mar 6, 2012
1,072
1,226
FWIW: I've been working at trying to fix MMS. The problem is that the APNs are not being loaded. It's not a problem with the APNs themselves but the loading, since we have no sim card I think. I've been looking at two potential fixes:

This one, from Pons for CM 10.2, was never completed and now fails to apply due to conflicts:
http://review.cyanogenmod.org/#/c/52672/

This one, from Evervolv JB 4.3, applies cleanly but breaks the build:
http://review.evervolv.com/#/c/9024/

I was hoping to get it working today and post another build but no joy.
 

zachf714

Senior Member
Jun 4, 2012
3,596
984
Mooresville
Regarding the 3.x kernel, technically we should be able to slowly move 2.6 up the line with code Aurora and korg

Sent from my SCH-I535 using Tapatalk
 
  • Like
Reactions: tydiamond11

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,327
5,060
FWIW: I've been working at trying to fix MMS. The problem is that the APNs are not being loaded. It's not a problem with the APNs themselves but the loading, since we have no sim card I think. I've been looking at two potential fixes:

This one, from Pons for CM 10.2, was never completed and now fails to apply due to conflicts:
http://review.cyanogenmod.org/#/c/52672/

This one, from Evervolv JB 4.3, applies cleanly but breaks the build:
http://review.evervolv.com/#/c/9024/

I was hoping to get it working today and post another build but no joy.

If data still doesn't work MMS won't since MMS has to connect to the 3g network. I haven't followed this thread closely enough to see if data is working now.
 

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,327
5,060
I'm in agreement with Pons. i read half the article on Snapchat and it's enough to make me not want to use it and encourage others to do the same. I'll all for helping people fix issues but should we help when the issue is to fix an insecure app that the developer has done nothing to fix when pointed out months ago?

On the torch thing, it's not HTC's torch app if it's AOSP. I'm not sure why it needs to be world writeable. I'll have to see what permissions are set on my m7 later.
 

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,327
5,060
All jb 4.3 roms and Kitkat roms use different blobs than 4.2 because they don't support ion but 4.1 does not support ion either so I assume 4.1 uses the same blobs

Sent from my SCH-I535 using Tapatalk

Umm, 4.4 does use ion on qsd8k devices:

https://github.com/Evervolv/android.../configs/evervolv_incrediblec_defconfig#L1507

From the logcat, this is what we're using for kitkat:

I/Adreno200-EGL( 4395): <eglInitialize:269>: EGL 1.4 QUALCOMM build: Nondeterministic AU_full_mako_PARTNER-ANDROID/JB-MR1-DEV_CL2961380_release_AU (CL2961380)

Antutu says OpenGL ES 2.0 V@6.0. So they're V6 of the drivers so they're quite old. It may need a lot of kernel updates to work with newer drivers.
 
Last edited:

zachf714

Senior Member
Jun 4, 2012
3,596
984
Mooresville
Umm, 4.4 does use ion on qsd8k devices:

https://github.com/Evervolv/android.../configs/evervolv_incrediblec_defconfig#L1507

From the logcat, this is what we're using for kitkat:

I/Adreno200-EGL( 4395): <eglInitialize:269>: EGL 1.4 QUALCOMM build: Nondeterministic AU_full_mako_PARTNER-ANDROID/JB-MR1-DEV_CL2961380_release_AU (CL2961380)

Antutu says OpenGL ES 2.0 V@6.0. So they're V6 of the drivers so they're quite old. It may need a lot of kernel updates to work with newer drivers.

Ok, I thought they went back to the old pmem drivers

Sent from my SCH-I535 using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    Since Evervolv 4.0.0 is getting pretty usable for the good old Droid Incredible, I thought it was time it had its own thread. These builds are still considered experimental. If the Evervolv team decides that things are stable enough to turn on nightly builds, I will update the OP and stop posting my own builds.

    If you have a problem, I'll listen but don't necessarily expect me to fix it. It's not that I'm grumpy, I'm just not that good.

    Working:
    - Calls / sms
    - WiFi
    - Mobile Data
    - Camera
    - sdcard and emmc access from phone
    - USB Mass Storage for sdcard and emmc
    - ART (Use at your own risk)
    - A bunch of other stuff

    Not working:
    - Video camera
    - MMS
    - Video hangouts
    - Probably more stuff

    This ROM is now part of xda DevDB!
    Downloads are in the tab up top. ^^^

    Gapps:
    https://www.androidfilehost.com/?fid=24052804347820768

    Many thanks to @tiny4579 for getting this booting and fixing sdcard/fuse issues.
    Many thanks also to the Evervolv team.
    And finally, thanks to all the brave souls who test and run this ROM!

    Previous thread: http://xdaforums.com/showthread.php?t=2046220

    Information on Evervolv:
    Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven. The Evervolv Project is made up of numerous members and contributors.

    Here's a couple links to keep in mind:
    Evervolv Github: https://github.com/Evervolv
    Evervolv Gerrit: http://review.evervolv.com/
    Evervolv website: http://www.evervolv.com/

    IRC: #evervolv

    [GPL Compliance]
    Kernel Source: https://github.com/Evervolv/android_kernel_htc_qsd8k

    XDA:DevDB Information
    Unofficial Evervolv 4.0.0 (Android 4.4.x kitkat), ROM for the HTC Incredible

    Contributors
    musical_chairs
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 2.6.x
    Based On: Evervolv

    Version Information
    Status: Testing

    Created 2014-09-27
    Last Updated 2014-09-27
    7
    New build is up, I won't be able to test it until tonight, so flash with caution until I or someone else confirms that it is working:
    http://d-h.st/mPU

    Edit: The Inc is back in the house, so I can test now. ROM works fine, though MMS is still not working.
    6
    An update happened:
    d-h.st/FDO
    I don't know of any significant changes, and no, I did not fix MMS. Oh, and ART does work.*

    * first boot after changing to ART from Dalvik takes forever, and it took a few reboots to get everything to settle in, and the first launch on most apps was really slow...but after all that was over it actually seems to work quite well.
    6
    New build up: http://d-h.st/shm

    There are a few new Evervolv goodies, nothing else immediately noticeable.

    Note: If you're compiling this ROM yourself, this change causes massive amounts of soft reboots, so I have reverted it for now until I can figure out something better.
    6
    no new version will be?:(

    Sure, I can build a new version. I was holding off, hoping for a fox for MMS, but I am stumped on that at this point. I'll try to post a new build in the next few days.