Database Develop

[Update]Proximity Fix for Kexec Kernels! - All Sensors

First things first, I'd like to wish you all hello, as this is my first post here and to XDA in general.
That being said, after getting much out of XDA over the years I figured I would try to give something back while experimenting with android!
I give you..
Droid 3 Custom Sensors Module
This enables/fixes our proximity sensor on hashcode's awesome kexec kernel so the phone screen blanks during calls!
The issue is with the sensors.solana.so proprietary library that comes with our phones from motorola.
So I compiled for us a new sensors.solana.so to use which is compatible with Kexec kernels.
Note: This library only controls accerometer sensor, light/prox sensor and orientation/magnet sensor so theoretically it should work the same, just with proximity working. But without more use I can't be sure.
Also in theory this should work for any flavor of Kexec releases, but I can only confirm cm10 currently...
Update[12/13/12]:
-Akm module is now working (Magnetic Field sensor / compass)
-Why is this useful?
Google maps should work better in terms of orientation
Compass apps should work now, along with any others that use rotation vector
-This required a driver edit to get it pointing in the right direction, so v2 includes newest hashcode kernel with the edit. i sent the code to hashcode, so hopefully if he incorporates these changes then this will no longer be needed.
Installation:
1. Download Custom-SolanaModule-v2[Kexec].zip
2. Install it like any other zip in ss3
Removal:
2. Download Stock-SolanaModule [Kexec].zip
2. Install it like any other zip in ss3
More Notes:
Attached also is the source code I used. I cannot claim writing most of it, as its more of a collaboration of various files that I found online for our sensors with a couple various tweaks.
Edit[12/13/2012] For anyone looking to implement this, just unzip v2 source code into root directory of your repo, files should go where needed.
Obviously a big shoutout/thanks to Hashcode/dhacker/jonpry and everyone else that got our D3's to the place they are now. This is just one more step in the right direction hopefully.

Thanks dudeeeee!! Someone should pm this to hash! It's great!
Enviado desde mi DROID3 usando Tapatalk 2

Confirmed. Good work.
Sent from my XT862 using xda app-developers app

Nice, one step closer.
Who twittered Hash?

I tweetered.

Thank you Jarveson!
I'll get this into new builds w/ a credit to you for getting this together.

Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Also, Thanks Hash! I forgot to say that it would be awesome if you were able to incorporate this in your new builds, it was really late/early when I typed that up initially

jarveson said:
Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Click to expand...
Click to collapse
Orientation is already working not sure about magnet

DoubleYouPee said:
Orientation is already working not sure about magnet
Click to expand...
Click to collapse
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.

hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
djbolden said:
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.
Click to expand...
Click to collapse
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch

jarveson said:
hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch
Click to expand...
Click to collapse
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.

DoubleYouPee said:
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.
Click to expand...
Click to collapse
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?

jarveson said:
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?
Click to expand...
Click to collapse
Ye sometimes when I wake the screen it's in landscape. Or other way around when I open the keyboard it doesn't wake. If I then press a key it wakes but is still in portrait.
Btw, I also need to reapply auto brightness occasionally because it doesn't stick to my custom light sensor settings. But that might be some bug because the sensor itself works fine
Oh, thanks for the work btw. Only camera "sensor" left now

Ok, i can see the magnet works now in GPS toolbox, thanks!
I should've mentioned that I'm not using auto-rotate - so the problem I described is probably not related to these sensors.
It seems that sometimes, it doesn't recoqnize that the QWERTY keyboard got closed or got opened, and therefore it sticks the either landscape or portrait.
This doesn't happen in GB, so it's not a hardware fault on the slide mechanism.

What is libsensors? and do I need to install libsensors to use your custom proximity sensor?

Own Demon said:
What is libsensors? and do I need to install libsensors to use your custom proximity sensor?
Click to expand...
Click to collapse
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore

jarveson said:
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore
Click to expand...
Click to collapse
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).

Own Demon said:
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).
Click to expand...
Click to collapse
Coming after the 1/23 nightlies or do we know when?

Well actually i think nxt build well include this.
Sent from my XT862 using xda app-developers app

[wip][kexec] [aokp and cm10] jb 4.1.2

New Builds - December 30 - I don't know if anything changed, I just sync'd repos and compiled it. But it's newer, eh!
MAKE SURE YOU WIPE DATA/CACHE AND SYSTEM AND INSTALL THIS ROM TO A FRESH ROM SLOT. Don't complain about non-working or strangely behaving apps if you flash over an old install without trying this first.
Based on the work of the All-Powerful Hashcode (source), here are fresh builds of AOKP JB and CM10.
Still no working camera. However, includes the sensor fix from Jarveson (Thanks!). HW codecs re-activated (thanks Hashcode!)
Updated repos, minor tweaks to get it to build correctly (Solana github repo doesn't build successfully as-is). See the posts ~ pg 153 of Hashcode's official thread.
Use gapps 20121011 available at your nearest filehost.
Download:
/mediafire/solana
For our friends on the other side of the Great Firewall:
CM10 Dec 15
These are ALPHA test builds (as noted by Hash) and a constant work in progress. I recommend flashing into a secondary ROM slot until you feel comfortable.
Thanks to Hashcode, dhacker, jonpry, jarveson, Google, AOKP, CM and everyone else who made this possible.

Kernel Included? version?
Gapps included?
Thanks for your work on the D3
Oh yeah, FIRST
Always wanted to do that

Thanks for this! I will finally test it today (didn't have time).
Maybe you're interested in including the fix I use for making the D3 wake with keyboard keys also.
For me at least, it was one of the first things I missed on kexec ICS/JB.
http://forum.xda-developers.com/showpost.php?p=33639782&postcount=1333
Will report back later today

If possible, could you please make a CM10 version?
AOPK has
1) No profiles
2) Brightness toggle is on separate row
3) Can't use 4x4 unlock slide
4) ....

I'm running it. So far so good.
Sent from my XT862 using xda app-developers app

DoubleYouPee said:
If possible, could you please make a CM10 version?
AOPK has
1) No profiles
2) Brightness toggle is on separate row
3) Can't use 4x4 unlock slide
4) ....
Click to expand...
Click to collapse
Awesome build, but I'm looking forward for a Cyanogenmod build as well.

CM build
I'll start a CM10 build tonight or tomorrow, depending on how I'm feeling. Been a busy weekend working and lots of late nights getting just AOKP to work cuz it's my primary.
In theory it shouldn't be too difficult, because AOKP is CM based. But I'm no professional, I just do this for the enjoyment.
Will keep you guys posted.

sylentprofet said:
I'll start a CM10 build tonight or tomorrow, depending on how I'm feeling. Been a busy weekend working and lots of late nights getting just AOKP to work cuz it's my primary.
In theory it shouldn't be too difficult, because AOKP is CM based. But I'm no professional, I just do this for the enjoyment.
Will keep you guys posted.
Click to expand...
Click to collapse
If it's CM based I wonder why they've removed so many features
Thanks!

DoubleYouPee said:
If it's CM based I wonder why they've removed so many features
Thanks!
Click to expand...
Click to collapse
... because... because... it's more... aerodynamic?
(CM10 building as we speak)

sweet!,
what about the bluetooth issue? all gone?

I do understand that you are working off of Hash codes work....
Just a heads up. I do believe you are required to list links to source for GLE standards. This includes link to source for ROM as well as Kernel.
Great work thus far and thank you for your efforts:thumbup:
Sent from my Galaxy Nexus using xda premium

Awesome CM 10 build, enjoying the proximity sensor fix, but didn't you say that MMS was fixed on Verizon? It still says "Invalid recipient" for me. Anyone else?

hilokilo said:
Awesome CM 10 build, enjoying the proximity sensor fix, but didn't you say that MMS was fixed on Verizon? It still says "Invalid recipient" for me. Anyone else?
Click to expand...
Click to collapse
I've been talking to another user about this. Turns out that the stock messaging app is still affected by the MMS bug. I've always used a third party app so I didn't notice when I did testing. Sorry everyone.
But it works with a third party messaging app definitely. GoSMS is my present choice. Used to be Handcent but it's gone down the drain IMO the past year.

Yes mms no workie in stock. Go sms seems to work though.
Sent from my XT862 using xda app-developers app

Hmm MMS works on the 883 radio from T-Mobile. Maybe it's something in build.prop? Maybe it's APN settings? I think CDMA carriers still use APNs.

Already went down the road of apn. Everything was correct in mine. Went ahead and deleted and re entered, no change in built in sms/mms app. Wouldn't know what to check in build.prop.
Sent from my XT862 using xda app-developers app

Installing CM10 version now.
Btw it baffles me you guys still use "MMS" :silly: that's like saying you still use CDs :laugh:
edit: flashed right over my old CM10 build..lets see what happens. It works for now
edit2: First thing I noticed, my generic.kl didn't work. Apparently, now I have to edit omap4-keypad.kl. No idea why:
http://dl.dropbox.com/u/22072961/Droid 3/omap4-keypad.kl

DoubleYouPee said:
Installing CM10 version now.
...
edit: flashed right over my old CM10 build..lets see what happens. It works for now
...
Click to expand...
Click to collapse
I did the same and it seems to be working well. I've only had one phone call and the phone app did crash when the call ended. I *think* the called party hung up first. The sensor fix is very nice - I was somehow regularly getting into the settings menu with my ear and changing stuff before it
I think the only thing I miss at this point is the audio out via the car dock special usb cable. I've thought about trying to help figure that one out, but the last programming I did was in the late 80's in C, so the learning curve is gonna be kinda steep. I have installed the sdk on my Fedora machine. We'll see if I can get motivated to figure out how to actually do anything with it.

djbolden said:
I did the same and it seems to be working well. I've only had one phone call and the phone app did crash when the call ended. I *think* the called party hung up first. The sensor fix is very nice - I was somehow regularly getting into the settings menu with my ear and changing stuff before it
I think the only thing I miss at this point is the audio out via the car dock special usb cable. I've thought about trying to help figure that one out, but the last programming I did was in the late 80's in C, so the learning curve is gonna be kinda steep. I have installed the sdk on my Fedora machine. We'll see if I can get motivated to figure out how to actually do anything with it.
Click to expand...
Click to collapse
If you understand C well, you might actually not have too hard a time, especially if Android is C++. I have no idea though.

set up
if anyone would like to get their machine going for development, i made a blog post (my first serious one ever) about setting up Ubuntu 12.10 properly to compile Android from source.
https://soupdawg.wordpress.com/2012...-for-building-android-jellybean-all-variants/
all the other guides i've seen are up to 12.04, and setting up the correct JDK is unique on 12.10
good luck everyone!
NOTE: my process.phone always crashes after calls. it doesnt seem to impact anything, i still run it day to day just fine. i'll try to track it down and see whats up. i think it's because of the hack i had to do to get the ROM to compile correctly. frameworks/base in its natural state from the repo causes build errors.

[ROM][UNOFFICIAL] Pons CM10.1 Inc builds (WEEKLY)

CM10.1 Pons
Goo.Im Download
Tiny's Gapps
(currrently recommended due to their smaller size, and until I get around to making an updated one)
Goo.Im Gapps
(untested)
Merged Commits for Jellybean
(aka Changelog)​
What this ROM is:
Stripped version of CM10.1 (to make it fit) using tiny's/chad's incredikernel synced and compiled from source
Uses only CM10.1 source, and...
missing components from Evervolv
incredikernel source from tiny4579
and my HTC Incredible device tree
Now supports OTA updating via the Goo Manager app
My change log (major changes that deviate away from CM10.1)
20130303
Initial release
Added Status bar battery mod
Replaced ChainsDD Superuser with Koush's embedded Superuser
Removed (with my suggested replacements, if any)
ChainsDD's Superuser (this ROM uses Koush's embedded Superuser instead till it gets merged)
CMUpdater (only shows official, CM7, builds for the Inc; use the included Goo Manager app for CM10.1 updates)
CMWallpapers
Music
MusicFX
Nfc
Protips
SoundRecorder
SpareParts
Terminal Emulator (available from the Play Store)
VideoEditor
Basic wallpaper
Galaxy4 wallpaper
HoloSpiral wallpaper
MagicSmoke wallpaper
MusicVisualization wallpaper
NoiseField wallpaper
PhaseBeam wallpaper
Known issues:
Watching YouTube videos flickers occasionally
Camera preview is glitchy with stock app; use a 3rd party one instead
Video camera has a very low fps (it stutters)
Laggy at first, due to filled system space (let it settle, then delete any system apps you don't need)
anymore, let me know
Source/Sauce (in case you missed it)
CM10 (I use their manifest.xml)
Evervolv (I use parts of their frameworks and other repoitories to fix qsd8k specific issues)
My device tree for the Inc
Incredikernel by tiny
For a complete list of what's added/removed/replaced from CM10's manifest, check my local_manfiest.xml
FAQ:
[Q] Pons, why are you compiling your own? Why don't we get official CM10.1 goodness?
[A] Well, now, why don't you take a gander at this: CyanogenMod: CM 9+, N1 (and other S1 SoC)
[Q] Gee, Pons, this here looks fun. How do I compile it myself?
[A] Here ya go, lil guy. Just follow these instructions: How to Compile CM10.1 for the Inc (if you encounter any issues using this to compile, please report here so I can troubleshoot and update if need be)
[Q] Why did you disappear?
[A] Long story short, my computer broke right before I went on a business trip. Now I'm stuck on a side of mountain, but only have a 256kbps internet, which has a lot of filters on it (I actually can't download from Goo.im; I have to ssh into my profile to download.)
[Q] Well, that doesn't sound pleasant. Are you back for good?
[A] Maybe, maybe not. Some good people are allowing me to use their build box, so that's how I'm maintaining right now. I'll keep it up, till I get moved again, or they decide to revoke my access.
[Q] Oh. That's cool. Onto what really matters: how often are you going to update?
[A] Will shoot for weekly, or bi-weekly (if major changes come out). The internet is painfully slow, and I don't want to abuse the build bot access I was given. Or until I move or get revoked access.
Credits/Thanks​
All credit goes to Cyanogen and the rest of the CM team, and especially our HTC Incredible maintainers, as listed by the CyanogenMod site: jistone (aka CUViper/This Guy), slayher, and of course, koush. Of course, don't forget about the Evervolv team, who have given our outdated qsd8k device a lot of love, despite being dropped by CM.
In addition, tiny4579 for his incredikernel, and for helping with my builds while I'm away.
For some reason, I have received several requests to put a donation link in my profile. You can always donate to the CyanogenMod project or the Evervolv project, but if you feel you HAVE to donate to me, I've put a link in my profile, and all donations will go towards upgrading my computer, so I can stay on top of this for CM10.2/11/and beyond.
Footnote: This thread is a WIP. I will probably restructure it and try to make it look pretty, and I might add a Q&A thread, depending on how many inane and repetitive questions I get that take away from development. I also didn't include any Launcher screen shots, since that is the easiest thing to change and theme. And I see that people have already tried the ROM, since I have 4 downloads so far, and 1 was me. Thoughts/problems?

Reserved....
Particularly let me know if there are any crippling bugs (or bugs period) that differ from what is listed as the known issues, and from tiny's.
Also, any issues with the embedded Superuser? It has had minimal testing, despite being put together by a ninja coder, Koush, and that is one reason it has not made it into CM10.1 Nightlys.

Great to have you back Pons. I'm having zero issues the new su. It seems to boot a little faster.
Sent from my ADR6300 using xda app-developers app

zombolt said:
Great to have you back Pons. I'm having zero issues the new su. It seems to boot a little faster.
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
It should boot a tiny bit faster, as well as su access being better/quicker. It's now an integrated part of Settings, as opposed to a separate app.
Bear in mind that Superuser is still a work in progess. Superuser and binary itself have 0 issues (that I can tell) as far as granting, prompting, denying, etc, but the app needs a little UX work. For instance, go into Settings > Superuser. Click the little icon at the very bottom, this opens up the log. Click the icon in the bottom left, and this does nothing. Koush is aware of these issues, and will correct them when he gets around to it. I'm more interested in if it (or Settings) FC, or if something is not getting root.
A user said:
there seems to be some UX inconsistency in the app. When i click on the log button it brings me into the log, which is fine. However, the button immediately becomes redundant in that said screen. It has no function whatsoever.
Also, i thought there should be a back function tied to the icon so that i can return to the main screen... no?
Click to expand...
Click to collapse

Koush said:
yeah, the icon behavior needs to be cleaned up. pressing back will take you back though.
Click to expand...
Click to collapse

Is there a way someone could work on the offline voice to text ? Is this going to replace tinys cm10.1 ROM ? Nice work!

Completely wiped phone, EMMC, SD. Took the opportunity to install TWRP, and had a blast playing around with it (used your .zip from that thread). Installed this ROM and Tiny's 2/7/13 GAPPS.
I'm not sure what issues will pop up from the flash-over crowd, but clean install was a flawless process. You guys keep giving me reasons to carry this phone. Well played, by everyone involved.

tydiamond11 said:
Is there a way someone could work on the offline voice to text ? Is this going to replace tinys cm10.1 ROM ? Nice work!
Click to expand...
Click to collapse
If you make enough room in the system partition and copy the correct libraries into the gapps zip before flashing offline dictation should work. It does on Tiny's, at least.
Out of curiosity, is there about significant difference between this and Tiny's? Pretty much just superuser?

mh0520 said:
If you make enough room in the system partition and copy the correct libraries into the gapps zip before flashing offline dictation should work. It does on Tiny's, at least.
Click to expand...
Click to collapse
I plan on getting to that in about a week or so, time depending.
mh0520 said:
Out of curiosity, is there about significant difference between this and Tiny's? Pretty much just superuser?
Click to expand...
Click to collapse
As far as the end user is concerned? There's that and the status bar battery mod, one of my favorite tweaks since my CM7 days. I don't know exactly what tiny throws in his, but I put in a couple of security hardening picks that most/all users won't notice or feel.
tydiamond11 said:
Is this going to replace tinys cm10.1 ROM ?
Click to expand...
Click to collapse
Probably not. Tiny and I generally work together to make CM10.1 better for the Inc. I opened this thread because I can compile and tweak stuff when tiny's busy, but I can't really test it myself. I don't have data, wifi, or gps on my phone where I'm at, and it takes me 3-5 hours to download each ROM. So I opened this to get a wider range of testers.

Good to have you back. Did you get faster internet?

zachf714 said:
Good to have you back. Did you get faster internet?
Click to expand...
Click to collapse
Nope, hence my 3-5 hour download of a 114 mb ROM.

tydiamond11 said:
Is there a way someone could work on the offline voice to text ?!
Click to expand...
Click to collapse
It works if you put the files into place, just like on Tiny's ROM. I modified Tiny's gapps, removed some stuff I didn't want and added in the offline files. I still have to delete some stuff from the ROM to make room for the offline files, so my gapss aren't share-worthy. But it works for me.
Valdigrieve said:
I'm not sure what issues will pop up from the flash-over crowd, but clean install was a flawless process.
Click to expand...
Click to collapse
No issues here. I did wipe /system (due to the way I install gapps with offlinevoice to text files) and cache (for good measure) before installing, but I didn't wipe any data.

PonsAsinorem said:
Nope, hence my 3-5 hour download of a 114 mb ROM.
Click to expand...
Click to collapse
Oh OK ... The goo build box is a good idea I think it would be nice to have access to .. It would make things easier for you to
Sent from my ADR6300 using Tapatalk 2

Any way to verify if fastcharge, does in fact, work?
Sent from my ADR6300 using xda app-developers app

zombolt said:
Any way to verify if fastcharge, does in fact, work?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Never really used it. From what I remember, though, it's a kernel tweak that chad put in. Tiny forked his tree, so unless tiny reverted the commit (which I doubt), it should still be in there (internet is way too slow for me to go digging around randomly). As for how to verify it's working, I completely forget. I'm vaguely sure a way does exist beyond watching it charge quickly, but can't remember.

zombolt said:
Any way to verify if fastcharge, does in fact, work?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Fastcharge is definitely an option in the kernel that ships with the ROM. It's off by default but the free incredicontrol can enable it. The only thing it does is enable the full charge speed for USB connections which is risky if it comes from a PC as the PC USB ports are only designed for 500mah of current. I've done it safely and i actually have fastcharge USB on by default on my inc but I still have to throw out the warning to be careful.
As far as verifying there are a few ways:
1. Check the value of /sys/kernel/fast_charge/fast_charge_usb. It's 1 for on and 0 for off.
2. Monitor mA current on USB charging and if it's over 500 mA then fast charge USB is working.
3. Check the kernel log in terminal ater plugging the phone into a USB connection, it should report switch charger (Fast) at the bottom.
su
dmesg | grep "Switch charger"

I am a big fan of fastcharge. Although battery health could be a factor, I am suspicious that both fastcharge and DSP manager have gone the way of budweiser served in Utah. My power supply used to get scorching hot and I could get a green light from empty in about 2 hours on the 3500 battery. Now I use the stock battery and it takes at least about 3 hours or longer to get it charged. DSP Manager still works, is much more subtle. I have had to resort to using a second eq app alongside DSP Manager to get levels right.
Sent from my ADR6300 using xda app-developers app

Work is ramping up, and so is school. No time to actually do more than minor tinkering, so thread is more or less redundant of tiny's. On that note, closed. I'll still try to push out weekly builds (tiny said I could post in his thread whenever I had a build), but no promises.

[WIP]Incredible Sense 4.1[Apr.22.2013][Working too]

DOWNLOADs:
1.7 BETA - Any future releases:
http://d-h.st/users/tiny4579
1.0 - 1.6 are:
http://d-h.st/users/Tribulattifather/
WORKING in ver 1.7 BETA so far:
WiFi - Thanks to Tiny4579
Cell Service- Earpiece, Mic and Speaker phone all work.
SMS - Text send and receive
Dialer - calls out and works during call
Compass - works in Speedview app
Music /Sound
Touch
USB in ADB
USB via UMS
Capacitive Buttons
ScreenShot
Extended Menu
Camera
NOT WORKING:
BlueTooth (Connects but doesn't read)
Data
GPS
Video Recording
WORKING ON ATM:
Data
EGL and GUI
When we are finished with the Beta Releases we will numerate regularly again with 1.0 as the first release candidate.
THANKS:
Big Thanks to Tiny4579 for getting Wifi working and for supporting the project with his kernel.
Big thanks to Greeneyes2910 for making this possible.
Thanks to Devs PonsAsinorem, Flagmax, Ljjehl and Zachf for the time they spent helping me bounce ideas off of.
Also a thanks to invisiblek and cmlusco for the base files.
And of course HTC too.
SCREENSHOTS:

Greeneyes is the one I just hit up for a wifi fix TheRiseM does not know much

Your main error is
Code:
AndroidRuntime(11867): java.lang.RuntimeException: Unable to instantiate application com.android.htcdialer.DialerApp: java.lang.ClassNotFoundException: com.android.htcdialer.DialerApp
Do you have HTC Dialer in the ROM?
(since I haven't really seen you around, I'm going to assume you don't really know my situation. I can help troubleshoot and give you ideas, but it takes me 5-8 hours to download these ROMs, which I'm not going to do because they change so frequently).

And I completely understand that situation; I used to have an issue with my cable for a week while they were fixing it. My net was as slow as adsl.
I was actually here about a year ago actively. But got an Evo3D and did my thing there for a bit. Now, I want the same things for Inc as my Evo had.

PonsAsinorem said:
Your main error is
Code:
AndroidRuntime(11867): java.lang.RuntimeException: Unable to instantiate application com.android.htcdialer.DialerApp: java.lang.ClassNotFoundException: com.android.htcdialer.DialerApp
Do you have HTC Dialer in the ROM?
(since I haven't really seen you around, I'm going to assume you don't really know my situation. I can help troubleshoot and give you ideas, but it takes me 5-8 hours to download these ROMs, which I'm not going to do because they change so frequently).
Click to expand...
Click to collapse
I think the dialer is there .... if you want I can make a mirror as I am working on the project to that may have faster down speeds

So far, I've fixed the Camera and the acore issue and the dialer issue.
It's uploaded now also.

zachf714 said:
I think the dialer is there .... if you want I can make a mirror as I am working on the project to that may have faster down speeds
Click to expand...
Click to collapse
It's not your or his end, it's the fact that I'm on an advertised 256kbps halfway across the world. And I say advertised as in I don't believe it. It's probably a lot lower.

PonsAsinorem said:
It's not your or his end, it's the fact that I'm on an advertised 256kbps halfway across the world. And I say advertised as in I don't believe it. It's probably a lot lower.
Click to expand...
Click to collapse
Oh ok I getcha .... That is seriously like my upload speed so I can see where your problem comes in

What I did so far was I took wpa_suplicant, wifitools and wpa_cli from the cm9 and copied over to bin.
Then I added :
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network = 4
ro.telephony.default_network = 4
wifi.interface = wlan0
wifi.supplicant_scan_interval=45
mobiledata.interfaces=rmnet0
ro.com.android.dataroaming = true​to the build.prop
Then made sure eth0 was changed to wlan0 in the conf files.
And then lastly, I took the wifi permissions from etc and copied over.
Also, added the base gps.conf
As of right now I believe I have cell service and/or data.
But not sure because I don't have a carrier for this device.
But I believe I did because the timezones don't have to be set manually anymore.
So I need some help testing it if it works or not.
Wifi is still a no go but it is getting better.
I don't see the same error messages I was seeing as before in the logcat.
EDIT: Just fixed Sdcard mount indevice. Can listen to music and view pictures now
Uploading ver 1.4 now.

I was gonna test the cell/dialer but dev-host is down atm.

ver 1.4 is up now.

Ok it looks like dev-host is back.
EDIT: Ok thanks. I will post my findings in this post so not to clutter.

Flagmax said:
Ok it looks like dev-host is back.
EDIT: Ok thanks. I will post my findings in this post so not to clutter.
Click to expand...
Click to collapse
Ah, clutter away, lol. Almost done uploading.
I'm about to head to bed but i will be on a different Rom on my phone and keeping an eye on it.
I can't wait myself to find out or not if cell service, data, gps and bluetooth work.

Well I amazed to see the progress! I want to congratulate everyone who is involved.
Works:
Cell Service- Earpiece, Mic and Speaker phone all work. Sound very loud but a little noisy in my opinion.
SMS - Text send and receive
Dialer - calls out and works during call
Compass - works in Speedview app
Music - plays through speaker
Don't work:
WiFi - error
Data - can't turn on
Bluetooth - can't turn on
GPS - checked but still don't work
Camcorder - crashes
Sent from my ADR6300 using Tapatalk 2

That is pretty good ! Keep up the good work!
God Bless Your Work!
Sent using my jb android phone!

ALRIGHT AFTER SOME TIME AND GOOGLE SEARCHING I FOUND THIS N1 THREAD .... The RAMDISK is the problem http://forum.xda-developers.com/showthread.php?t=1995549&page=15
I also just sent that dev a PM because he knows exactly what to do with the modules and ramdisk

zachf714 said:
ALRIGHT AFTER SOME TIME AND GOOGLE SEARCHING I FOUND THIS N1 THREAD .... The RAMDISK is the problem http://forum.xda-developers.com/showthread.php?t=1995549&page=15
I also just sent that dev a PM because he knows exactly what to do with the modules and ramdisk
Click to expand...
Click to collapse
Just curious, what makes you think that?
I scanned the page, and all I found was...
Aca902 said:
Made ramdisk modification... Fixed wifi
Click to expand...
Click to collapse
Do you have any more information/ideas on why it's the ramdisk? That quote is not much to go on, and contains zero information on how this is relevant to the inc's problem.

Last night the Dialer showed up and worked just fine. I flashed ToB rom in morning for few hours then did a full wipe and put 1.4 back on and now Dialer not showing up.

Flagmax said:
Last night the Dialer showed up and worked just fine. I flashed ToB rom in morning for few hours then did a full wipe and put 1.4 back on and now Dialer not showing up. Attached logcat. Btw, is it safe to post logcats?
Click to expand...
Click to collapse
Just to make certain I would download again from my link and see if that happens again. Also, make sure to do a full wipe including dalvik-cache, system, all data and even the boot.

PonsAsinorem said:
Just curious, what makes you think that?
I scanned the page, and all I found was...
Do you have any more information/ideas on why it's the ramdisk? That quote is not much to go on, and contains zero information on how this is relevant to the inc's problem.
Click to expand...
Click to collapse
Yeah I had read a few pages before that to and everything pointing to WiFi and Bluetooth is related to the modules and the ramdisk
Sent from my Nexus 7 using Tapatalk HD

[ROM][T810/T815][8.x] LineageOS 15.1 20180722 [ABANDONED]

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+
- backup everything before install
- wipe data before upgrading from LineageOS 14.1 or stock rom
Install:
- Flash zip in TWRP
- Don't forget about gapps (arm 8.1)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Known issues:
unstable fingerprint
stuff, I haven't checked
Download:
T810: https://drive.google.com/open?id=1LlC7jBfq3H9FuPKZeKdQ3KyuiglgJTYv
T815: https://drive.google.com/open?id=1ZXg6Oy_aSfYL4XoXovfPzQ9pZqD1XVmw
Device sources:
https://github.com/bonuzzz

Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.

halloarno said:
Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.
Click to expand...
Click to collapse
do you mean the orientation of touch sensor?

bonuzzz said:
do you mean the orientation of touch sensor?
Click to expand...
Click to collapse
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.

halloarno said:
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.
Click to expand...
Click to collapse
I will upload proper build tomorrow. Thanks for bug report!

Boom. Been waiting for 8.1 for 815 for ages. Thanks for your work can't wait to see how this progresses!! ?

bonuzzz said:
I will upload proper build tomorrow. Thanks for bug report!
Click to expand...
Click to collapse
Congratulations bonuzz very happy to hear your success thanks a lot for your work
Ok one more thing can I use your work to build a different os please man?

( seem to be blind (or stupid) - Can someone please point me to a working TWRP 3.2 for the T810 so I am ready when the new build drops? Thanks a bunch!)
Edit: Sorry, found it. Stupid indeed.

I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github

I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir

ripee said:
I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir
Click to expand...
Click to collapse
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...

Nice to see U back @bonuzzz, especially with such amazing things ?
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?

bonuzzz said:
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...
Click to expand...
Click to collapse
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.

Voytec83 said:
Nice to see U back @bonuzzz, especially with such amazing things
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?
Click to expand...
Click to collapse
Go away, spammer
ripee said:
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.
Click to expand...
Click to collapse
I have the same behaviour in tab s3, but I thought it is because of libs from another device. But it's very funny, in oreo rotation is in another side)
PS: I mean not only oreo builds...

Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz

ripee said:
Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz
Click to expand...
Click to collapse
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.

bonuzzz said:
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.
Click to expand...
Click to collapse
So why make the effort to build again? This is the same old story with you. One day, you are helpful and generous with your builds; the next day, you complain about not wanting to make any more effort than you had already made.
Please make a decision and stick with it: either do your best to fix the most basic functions and let someone like me help you the best way I can by building from your code often, and giving you full credit, so that we can all give you frequent feedback, or don't create any more threads and abandon the 2015 Tab S2.

widevine L1 support added. we dont need patched netflix apks anymore
@ripee I make roms for myself and share them with others. What's wrong with that? And yes, I'm helpful and generous when you write me pm. Just curious, nobody asked for help in public. And yes, everything is depends on my spare time.
Nougat builds are really abandoned. You don't believe me or what? Or I should to write anything else there when people ask for update builds?
I see you worry about my git. Calm down, please. Why do you think I upload sources for you? I uploaded sources for you and you published your builds just right after that without understanding what exactly changed and instead of help to fix remain bugs. I told you few months ago to choose one author and try to fix something. You didn't hear me. I don't need any credits. But I don't like liars, if we talk about one person here. And I don't want more "we don't care" teams here. I don't need any daily public builds. It will be disorganized development. At least no one else haven't tried to fix anything in my (nougat) sources...
So, in short, I will do what I want. I will upload builds when I want. I will add/fix/change in builds what I want and in my own priority. I spend my own time for that. Don't like? Don't use. Make something yourself. Stop depend from me and let me do my work. Thanks in advance.

I just saw Shiny thread here ^-^ . I look twice to make sure it is 815 not anything else.
Thank you very much. We all appreciated your work and effort.
If you want any help test, logcat or even setup machine for build I'm ready for that ^-*

bonuzzz said:
I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github
Click to expand...
Click to collapse
Thanks a lot. Appreciate your work for our Tab S2. Have a good day mate?