CyanogenMod ATT/Telus Q+& 4.3 - HTC One X+

CyanogenMod ATT/Telus Q+& 4.3
Right guys this is the Q&A Thread for the AT&T/TELUS (evitareul) ask questions and so on report bugs to me, NO OFF TOPIC i will update the 2nd post with bugs and so on.
Ask questions if you are unsure about something
Don't go off topic
I have only made this thread as a convenience, as i know you lot like to talk to us, but i will lock it if it goes super OT

Download CM10.2.zip
Hi, where I find the link to download the file cm10.2.zip, because it can not find it in the post. Thanks.

fredtrejo said:
Hi, where I find the link to download the file cm10.2.zip, because it can not find it in the post. Thanks.
Click to expand...
Click to collapse
You change the theme into XDA 2013, and you will find out the download tab in there.
http://forum.xda-developers.com/devdb/project/?id=1784#downloads

sorceforge said:
You change the theme into XDA 2013, and you will find out the download tab in there.
http://forum.xda-developers.com/devdb/project/?id=1784#downloads
Click to expand...
Click to collapse
Thanks, now I will download and test it.

CM 10.2 is Cool!!
I am sort of new to this... let me know if you want more information...
I did a quick test, Flashed with TWRP... did not load google apps.
Here is what I found:
- seemed surprisingly stable.
- No LTE, but HSDPA/HSPA works fine. Signal was weak and H to H+ to 4G switching seemed to happen alot.
- SMS worked
- placed calls, but not really useful due to the known audio issue.
- MP3 played great with Apollo
- Torch app crashed (LED comes on then app dies in less than a second)
- Status area circle was constantly spinning... not sure why it is there or what it means I think it is the battery indicator
-- Reboot and Loaded Google Apps from recovery.
- Status area circle no longer spinning
- Google Apps all seem to work fine.
- Downloaded MX Player and watched MP4... no issues.
Not sure about battery life... sucked it down from 65% to 45% in an hour and a half of constant use.
Actually quite nice... if you can get past the whole not able to make phone calls thing.

Hey Lloir, I was just wondering if the calls issue might be attributed in the kernel source, possibly a line of code left out. Like the words "Internal Mic" or something to that nature.. I was looking around the other day and saw a line somewhere, I'll ha e to screen shot it so you can see where I'm talking about. I'll try to get to post that later.

sledgeharvy said:
Hey Lloir, I was just wondering if the calls issue might be attributed in the kernel source, possibly a line of code left out. Like the words "Internal Mic" or something to that nature.. I was looking around the other day and saw a line somewhere, I'll ha e to screen shot it so you can see where I'm talking about. I'll try to get to post that later.
Click to expand...
Click to collapse
Ok brill, just give me the folder eg arch/arm/drivers then the file name
Sent from my Nexus 5 using Tapatalk

Lloir said:
Ok brill, just give me the folder eg arch/arm/drivers then the file name
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Evitareul / android_device_htc_tegra3-common
>forked from CyanogenMod/android_device_htc_tegra3-common
>android_device_htc_tegra3-common / BoardConfigCommon.mk
Obviously, I'm not sure, would this have anything to do with the lack of audio on lines 20-22:
# Audio
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := false
If not there, there has to be a in library specifically for calls that has the same basic fork like here on
Evitareul / android_device_htc_tegra3-common
>forked from CyanogenMod/android_device_htc_tegra3-common
>android_device_htc_tegra3-common / tegra3
Line 16 might have a line left out that might lead to configuring the in call audio.

sledgeharvy said:
Evitareul / android_device_htc_tegra3-common
>forked from CyanogenMod/android_device_htc_tegra3-common
>android_device_htc_tegra3-common / BoardConfigCommon.mk
Obviously, I'm not sure, would this have anything to do with the lack of audio on lines 20-22:
# Audio
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := false
If not there, there has to be a in library specifically for calls that has the same basic fork like here on
Evitareul / android_device_htc_tegra3-common
>forked from CyanogenMod/android_device_htc_tegra3-common
>android_device_htc_tegra3-common / tegra3
Line 16 might have a line left out that might lead to configuring the in call audio.
Click to expand...
Click to collapse
i love people like you, not 100% sure what XYZ is, but still willing to help and give some fresh eyes on this! don't stop
the #Audio lines, have been tested while set to true, BUT it can't hurt for me to reset them to true, while using the now correct audio blobs.

right now i'am looking for an alternative way to get the incall audio stuff going.
The only way it's going to work is if i'am able to use ALL of the audio files for it and none from the Inter X+ or the Inter HOX
and it's not going to work < 4.3 due to the above issue, and due to the audio files not being 4.2+ they don't exactly work properly on 4.3 either..... so i'm busy working on this and hoping HTC do release a sense5 rom for you guys... no this doesn't mean i'm taking a rest, i'am STILL going to be looking for ways to get this damned thing going....if anyone want's to help that would be EPIC *hint hint*

all hail the king the king is dead
enter the new king @Thömy

Lloir said:
all hail the king the king is dead
enter the new king @Thömy
Click to expand...
Click to collapse
Lol, why do you say that?

I am sticking to the Q&A thread as i will leave the dev thread for updates.
Thanks Lloir for the hard work, if you post any update to the 4.3 using your 4.2.2 base i'll be happy to test and report

nook'r said:
I am sticking to the Q&A thread as i will leave the dev thread for updates.
Thanks Lloir for the hard work, if you post any update to the 4.3 using your 4.2.2 base i'll be happy to test and report
Click to expand...
Click to collapse
OMG someone who can tell the difference
finally, thought someone like you was the holy grail

Lloir said:
OMG someone who can tell the difference
finally, thought someone like you was the holy grail
Click to expand...
Click to collapse
a dev and a comedian
I finally get a stable Multiboot Hackintosh, now i can download your git and play around with it.
Oh, btw nothing is holy about me, i promise u. LMAO

With the new leak does this provide access to the driver source is the call issue still going to be present?

trannygranny said:
With the new leak does this provide access to the driver source is the call issue still going to be present?
Click to expand...
Click to collapse
time will tell, here's to hoping it will be fine

Sorry for posting in the dev thread, still getting used to XDA's new layout.
Since I haven't installed a new ROM since February, is it safe to assume I'm on an old hboot version?

Hero_Lief said:
Sorry for posting in the dev thread, still getting used to XDA's new layout.
Since I haven't installed a new ROM since February, is it safe to assume I'm on an old hboot version?
Click to expand...
Click to collapse
yea if it's not 1.72+ you are on the old hboot (which i assume as no one has the sense 5 ruu)

Is there anyway to test calls without gsm?

Related

SGS2 roms

I know I will almost indefinitely be flamed for asking this, but oh well here goes.
When I first got my AT&T SGS2, I installed an international rom (villain) It ran perfectly fine other than the fact calls were not operating properly. I immediately jumped ship though scared for my phone's life. I reflashed stock and AT&T modem, but now that I think back on it- wouldn't having flashed the at&t modem remedied that problem? and if truly need be couldn't an at&t version kernel be flashed( i.e. Entropy's DD) Everything seemed to operate perfectly fine (install went well, booted properly, smooth homescreen, apps running great)
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Entropy512 said:
In theory, replacing kernel/modem (and making sure the ROM doesn't include a bootloader) should work - however this is untested.
I'm going to be trying it tonight with SensatioN, as I did like that ROM when "hellraised" on Infuse and someone requested it, and it's about time someone tries to do a "hellraise" on an I9100 ROM.
Click to expand...
Click to collapse
You go entropy. Awesome. I will be glad to test it for you if needed.
Sent from my SAMSUNG-SGH-I777 using XDA App
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Hammersuit said:
Very cool! I more or less figured as much but i'm not quite that daring. I would be willing to do testing as well ( Oh and Entropy, Sensation was the rom I was looking at ) I too came over from the Infuse.(Thanks for all the kernel love!)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1328110 - Once I get permission to do so from the SensatioN ROM dev, I'll post it in dev as a proof-of-concept with details of what I did to port it.
Note that I don't have too much time to continue maintenance of a ROM - it's not where my skillset lies and between Real Life and kernel work, I'm pretty busy as is! But at least this will provide a starting point for those that want to go further.
Click to expand...
Click to collapse
Ha! Completely understandable. Thank you so much though, this proof-of-concept is wonderful news. It would be most beneficial to see some ports of well-supported GT-I9100 roms such as villain and DLEV rom etc.
Looks like there might be some known issues with my PoC port then... as I said, I haven't tested outgoing audio much (this is much harder for me to test than dialing voicemail...)
task650 said:
you're correct bro. ports from i9100 roms are very possible. the one thing you will need to do is change some of the lib and bin files to rid the issues with the mic on in calls. i think ive successfully ported just about most of the i9100 dev section so far. lol. for personal use only. if you need some help just let me know.
Click to expand...
Click to collapse
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Entropy512 said:
Which files are those? I tried to find the relevant CM7 commit (since they had mic issues in calls) but couldn't find it.
I know that turning Samsung Noise Reduction off (or on? It's freaking unclear whether "on" is the current state or destination state in the menus) seems to work around the problem on a per-call basis.
Click to expand...
Click to collapse
When I get home tonight ill look at which files I had to replace for dlev rom and shoot them over to you. Might be tomorrow depending on how late though bro.

[Dev Only] Collaborative thread of ICS on HTC Evo View [Express]

Alright, this thread is for all developers to post their progress, sources, etc for other developers to work on. There will be NO tolerance of "Good job" "thanks" etc, just click the damned button on the bottom. Now, what I have so far, is found that the tiamat kernels from cayniarb don't even boot so no kernel logs from that. I assume jmz may have something to contribute with kernels.
Here's a port of the flyer ICS rom (not the one chaos is working on) for the view. It boots to a black screen but you can get a logcat. We have gotten it to the bootanimation before so it should'nt be hard to do. If someone posts logcats (since I don't have the view) I will still help out
Link: http://d-h.st/j4hep7wqbo35
Good Job and Thanks ...sorry i had to. But yeah, what we have now is looking like a kernel issue. I have source and Im looking at it but that DOES NOT mean, im going to be able to do something useful. lol.
What we really need is a good work over the kernel aspect.. I think cayniarb's done a decent job getting it initiated but he doesn't have a view to test it on :/
I only understand how to modify the source of existing kernels, getting AOSP kernel out of the source for whatever was tailored by HTC is way beyond my skill, so I look towards you guys for that.
We've have several guys trying to work on a kernel though, what's the status from each of their end? (Thought they were all working independently, etc)
sorry to jump in to this discussion, but had to know if development is under action here or somewhere else? WOuld love to see some progress with ics on View, cos right now my View is about to die... ive lost intesest in it. Its sluggish, slow and not optimized... have faith in you guys though
Gumby63 said:
Here's a port of the flyer ICS rom (not the one chaos is working on) for the view. It boots to a black screen but you can get a logcat. We have gotten it to the bootanimation before so it should'nt be hard to do. If someone posts logcats (since I don't have the view) I will still help out
Link:
Click to expand...
Click to collapse
Any chance you still have that port? I might be able to make some head-way if all we need to get this booting is kernel work.
Hmm well that port is really outdated. I tell you what, I will try and get a basic port going of the Sense 4.0 ROM of the flyer and upload that for you guys to mess around with hopefully you will be able to get a logcat out of it
Gumby63 said:
Hmm well that port is really outdated. I tell you what, I will try and get a basic port going of the Sense 4.0 ROM of the flyer and upload that for you guys to mess around with hopefully you will be able to get a logcat out of it
Click to expand...
Click to collapse
You're the man, thank you sir.
Well I'm trying to upload it and I keep getting stuck on 1% which is really annoying so I'll try again later.
You could possibly use the boot.img from the kingdom ICS leak (evo design 4g) since it's the same exact chip and pretty much the same Hw except for the screen(which could cause an issue?). I tried just booting that leak(only changing the partitions in the update-script to match the views) and of course it was a no go which I expected but had to give it a shot anyway. lol So then I edited the build.prop and copied over some libs (which I think is the problem since they are HC libs). I also unpacked both the stock HC boot.img and the kingdom leak boot.img. I'm thinking I have to make changes there but I dont know what to change. I dont even get logcat access just stuck at the HTC screen
graffixnyc said:
You could possibly use the boot.img from the kingdom ICS leak (evo design 4g) since it's the same exact chip and pretty much the same Hw except for the screen(which could cause an issue?). I tried just booting that leak(only changing the partitions in the update-script to match the views) and of course it was a no go which I expected but had to give it a shot anyway. lol So then I edited the build.prop and copied over some libs (which I think is the problem since they are HC libs). I also unpacked both the stock HC boot.img and the kingdom leak boot.img. I'm thinking I have to make changes there but I dont know what to change. I dont even get logcat access just stuck at the HTC screen
Click to expand...
Click to collapse
You could try changing the bootclasspath in the init.rc file of the ramdisk to that of ICS? I've read around before that doing that would make a port boot but I've never had such luck in doing so. If I could ever get this uploaded maybe I can try and help if it has a logcat.
Gumby63 said:
You could try changing the bootclasspath in the init.rc file of the ramdisk to that of ICS? I've read around before that doing that would make a port boot but I've never had such luck in doing so. If I could ever get this uploaded maybe I can try and help if it has a logcat.
Click to expand...
Click to collapse
Hi Gumby
If youve got a download path for the orig file i will try upload it if you want got quick internet so if you got the orig link i could hvae it uploaded within 30 mins
Let me know
Nope I don't even have a link yet, I'll try again today.
Sent from my PG86100 using Tapatalk 2
Okay so I couldn't get it uploaded to Goo.im but dev-host worked. Here's the link to the sense 4.0 port.
http://d-h.st/QQ6
This will not boot. Hopefully someone can download and get a logcat out of it though.
Gumby63 said:
Okay so I couldn't get it uploaded to Goo.im but dev-host worked. Here's the link to the sense 4.0 port.
http://d-h.st/QQ6
This will not boot. Hopefully someone can download and get a logcat out of it though.
Click to expand...
Click to collapse
logcat: http://pastebin.com/dSmTH2gc
http://forum.xda-developers.com/showthread.php?t=1598713
Maybe this can help you guys with your progress
Sent from my PG41200 using xda premium
the key is this
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
once u got that itll boot..
Well I'm visiting my grandparents and cousins this week and I won't be home until Saturday. So until then I won't have WiFi and I won't be able to help out at all
When I get back I'll see what I can do though
Sent from my PG86100 using Tapatalk 2
I know this is a Dev Only thread, but has anyone started a Donation Pool ($$$) yet for getting ICS on the View 4G? I would be willing to contribute...
theorie said:
I know this is a Dev Only thread, but has anyone started a Donation Pool ($$$) yet for getting ICS on the View 4G? I would be willing to contribute...
Click to expand...
Click to collapse
I'll be honest with you, I dont think I have ever really seen a donation pool thread work out the way it should. The donation pools that do usually work better are "get so and so dev this device" (as long as the so and so dev is a well known dev, well respected already yada yada yada)

[Q] Any ICS ROM have camera working yet?

Same as title. I only use the Touchpad for Skype video.
No
Sent from my touchpad via tapatalk
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
Like he said, no.
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
If you only use Touchpad for Skype, why dont you boot into WebOS. Skype video working perfect there.
Sent from my AT&T Galaxy Note - please forgive if typos
Yeah this is what I'm going to have to do.
That's not exactly a bad thing... webos is great. it has better battery life than I've and Skype is good on it. I don't see any problems with it.
Sent from my HP TouchPad
webOs
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
Webos supports skype very nicely if this is all you use the touchpad for.
I have ICS on mine as well and most of the time I use webOs seems to support almost every site i go to. I have only found a few site it wont work on,Netflix windows live, Hulu.
I use ICS for netflix dont use Hulu and for windows live i just use the webOs email client and hotmail or windows live works fine.
The only thing I am trying to find is a book reader that views text files and has a bookmark or save page function in it , Ics has kemsoft and works but many times bookmark wont work .
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
No.
And aren't there already like 10 other threads about this?
Still no.
[5 minutes later]... Still no.
Camera is most likely not going to be working for a very long time, despite HP releasing the source for the hardware (or are they still delaying it) and its the last on the priorities list for any developer. I suggest use WebOS for skype cuz that works brilliantly
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Mast3rmatt said:
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Click to expand...
Click to collapse
The sarcasm looks strong with that one.
mkosem said:
The sarcasm looks strong with that one.
Click to expand...
Click to collapse
Hmm I guess I read it in the wrong way
Thanks
Mast3rmatt said:
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Click to expand...
Click to collapse
The camera will be fully functional in two weeks. If not, read this again
I really want the camera n mic to work too. Is the ics kernel or driver the problem?
hyperfire21 said:
I really want the camera n mic to work too. Is the ics kernel or driver the problem?
Click to expand...
Click to collapse
This is not the place to pose this question. The place to ask would be Rootzwiki, where the dev's can be found. There you'll find changelogs and sourcecode for just about everything, and you can certainly make changes and compile it yourself.
If you honestly and seriously know what you're talking about, and think you can help, the dev team would probably be very appreciative of assistance. Meaning, if you can code that stuff, great- lend a hand. But if you're just curious, then try to research your question without nagging the devs. They work hard, and for free. You could begin researching the topic, here.
Now, in answer to your question. I could be wrong. I'm just a simple Java/C# coder who can also do a bit of web. But it was my understanding that the driver is the issue. The source code for the kernel has been released, but (also as I understood it, I could be wrong) the entire kernel was not released. The drivers for mic and cam, however, were not released (again, if I understood correctly). So there's the problem. And further, the cam and mic are not at the top of the devs' list of priorities. They are working on other stuff that they feel is more important, about which I tend to agree, unknowingly. I mean, they recently (in the last 4-6 weeks) got us hardware acceleration working (in several applications, but not all). What I mean to say, is that there are bigger fires to be put out that users don't typically see as fires. But also, the cam and mic drivers not being released is a pretty big chunk of code. AFAIK they were going to have to begin to write these from scratch, which is a pretty hefty challenge that they've chosen not to undertake at this point. That's their prerogative, and I'm not going to nit-pick about that.
Basically, if you need cam and mic, you can install CM7 (which has bugs of its own) or you can boot into webOS. Those are our options at the moment.
sean is here. said:
Basically, if you need cam and mic, you can install CM7 (which has bugs of its own) or you can boot into webOS. Those are our options at the moment.
Click to expand...
Click to collapse
Or learn software development and learn to write drivers and contribute!
Personally, I know I can't code worth a damn, so I just accept what other people write.

[Q] Any way to get noticed if there is an Update of the Preview?

As the title says, i'd like to know, if there's any way to get notified if they have an update for the preview.
Or any page which will contain update notes in the future.
Mostly because i'd really like to use it, play with it and try some programming for it.
the problem is, i only got the nexus, so i have no spare phone.
(even though phone and sms is working, without music I can't live and no, i won't buy an extra mp3 player)
Anyways, would be great if anyone knows a way to get notified.
Else i'd suggest we may start an update thread here(?)
that way i could subscribe to that and look into it when I see it gets 10 pages per hour or so, lol
http://cdimage.ubuntu.com/ubuntu-touch-preview/
I don't think they're going to do much more work on Quantal. Raring will probably be merged in the near future. I check that page periodically to see if they sneak an update in.
Sent from my Galaxy Nexus using Tapatalk 2
lol daily-preinstalled NOW ON cdimage.ubuntu.com
MikeyCriggz said:
http://cdimage.ubuntu.com/ubuntu-touch-preview/
I don't think they're going to do much more work on Quantal. Raring will probably be merged in the near future. I check that page periodically to see if they sneak an update in.
Click to expand...
Click to collapse
lol MikeyCriggz look now: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/ yes there are daily builds
looks good, but how do I know what exactly changed?
GotDamned said:
looks good, but how do I know what exactly changed?
Click to expand...
Click to collapse
Nobody knows...
Hello,
A Mobile version of the Ubuntu "Update Manager"/"Software Upgrader" will be in the works soon, and definitely be done prior to release. So far, the only thing close to a changelog that I have been able to find is on their "Phablet" site. I have documented the details here - http://forum.xda-developers.com/showpost.php?p=38547205&postcount=19
GotDamned said:
looks good, but how do I know what exactly changed?
Click to expand...
Click to collapse
You can watch the Changelog file: cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/raring-preinstalled.changelog
Note that when the daily images switch from Raring to Saucy, the URL above will need to be changed.
mhall119 said:
You can watch the Changelog file: cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/raring-preinstalled.changelog
Note that when the daily images switch from Raring to Saucy, the URL above will need to be changed.
Click to expand...
Click to collapse
I have some doubts mich,
First, will we see any importante change when moving to Saucy in ubuntu touch?
Second, when I check milestone dates release here https://launchpad.net/ubuntu-touch-preview/+milestones I see that they dont follow these dates, no one has been "released". I have no clear how different fixes commited are realeased, could you explain it a bit?
Thanks man!
macpherson1999 said:
I have some doubts mich,
First, will we see any importante change when moving to Saucy in ubuntu touch?
Second, when I check milestone dates release here https://launchpad.net/ubuntu-touch-preview/+milestones I see that they dont follow these dates, no one has been "released". I have no clear how different fixes commited are realeased, could you explain it a bit?
Thanks man!
Click to expand...
Click to collapse
Those are milestones, not release dates. Milestones are what we use to target work items. It doesn't mean we're going to tag a 13.06 release image, it just means those are the work items we hope to have done and in the daily images by the end of June (or whichever month the milestone is for). The changelog I posted is the best way to see what is changing between each of the builds.
mhall119 said:
Those are milestones, not release dates. Milestones are what we use to target work items. It doesn't mean we're going to tag a 13.06 release image, it just means those are the work items we hope to have done and in the daily images by the end of June (or whichever month the milestone is for). The changelog I posted is the best way to see what is changing between each of the builds.
Click to expand...
Click to collapse
Oooookay, I see. Thanks a lot!

New Kernel Development! New features we all would like.

With the release of the bump website imminent many New Kernels are being developed. I just wanted to create a thread where we can focus on Kernel discussion. We can talk about requests and features we want added. We can talk about removal of screen sharpeneing. There is a lot on the Horizon with this phone and I'm super excited for development.
Delete . I posted on the wrong thread.
jmotyka said:
Im not getting any fc's on the messaging app.??
Click to expand...
Click to collapse
I'm slightly confused.
Maybe he is saying he misses those and would like a developer to look into adding them back in randomly ?
We are Android, we are diverse !
trent999 said:
Maybe he is saying he misses those and would like a developer to look into adding them back in randomly ?
We are Android, we are diverse !
Click to expand...
Click to collapse
lol That was great. If anybody spots this thread in the wild and is testing for an aosp Rom. I'd like to ask if they've corrected screen sharpening? It's a pretty annoying feature.
Dunno if it's related to kernels or not, but I'd really like a permanent fix for the voicemail notification issue. I've tried most the solutions floating around here, but nothing seems to stick.
Sent from my VS985 4G using Tapatalk
low volt kern with a USB fast charge is all I need

Categories

Resources