UPDATE 7/6/15: CM 12.1 is messed up again. I don't know. just find a rom that doesn't have a baked in DPI changer...
UPDATE 6/2/15: The newest nightlies of CM12.1 have a fix in place. It is filtering down into some of the custom roms as well (see below)...
UPDATE 6/9/15: The newest nightlies of CM12.1 have removed the fix. This is getting annoying.
UPDATE 6/16/15: I am going to stop maintaining this thread. AOSiP is the rom to go with for those wanting to keep Andoid Auto functionality in place.
So I have an annoyance that I wanted to see if anyone else was experiencing. I recently got a Pioneer AVIC-8100NEX head unit that has android auto built in. When I am using a stock based ROM, the android auto works fine. When I am running a CM/AOSP based ROM (with built in DPI changing), the picture is like zoomed in and is totally unusable. I can even run a stock based ROM with custom kernel and it runs just fine. I am currently running meanpop with code blue kernel and it works fine, I just miss a lot of the features of the other Roms that I can't get it to work right on.
Roms that work:
Stock
AOSIP (updated 6/16/15)
I just realized the background wallpaper is the same on both. This is driving me nuts!!
So its like it is just outputting the navigation buttons and "status bar" at the wrong resolution...??
Have you tried adjusting the dpi in chroma to see if it helps at all?
s2kpdx said:
So I have an annoyance that I wanted to see if anyone else was experiencing. I recently got a Pioneer AVIC-8100NEX head unit that has android auto built in. When I am using a stock based ROM, the android auto works fine. When I am running a CM/AOSP based ROM, the picture is like zoomed in and is totally unusable. I can even run a stock based ROM with custom kernel and it runs just fine. I am currently running meanpop with code blue kernel and it works fine, I just miss a lot of the features of the other Roms that I can't get it to work right on.
Roms that work:
Stock
MeanPop
Sinless
CleanROM
They look like this on the head unit (how they should):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Roms that do not work:
CM12.1
Chroma
Euphoria
Resurrection Remix
Benzo
BlissPop
Temesek 5.1
OptiPop
They look like this on the head unit:
Anyone experiencing this as well or know what the heck the issue could be??? I kinda think it might be an easy fix for someone that knows that they are doing (not me!).
Thanks in advance!
Click to expand...
Click to collapse
The problem is, I'm pretty sure none of us devs even have android auto to even begin to know where or what needs to be done to fix it
sykopompos said:
The problem is, I'm pretty sure none of us devs even have android auto to even begin to know where or what needs to be done to fix it
Click to expand...
Click to collapse
Yeah that's what I am thinking too. Its just so odd that it looks normal on all stock based Roms, but on any cm/aosp ROM its displayed incorrectly... Just has me stumped.
Ok, I have finally figured out that it is directly related to the rom having a built in DPI changing option in settings. All roms that have this do not work, and all that do not, work. Plus if I make extreme changes to the DPI using that setting, it is reflected a tiny bit on the head unit.
So next question... How difficult would it be to remove that built in DPI changing from one of these roms and see if that is enough to fix it???
s2kpdx said:
Ok, I have finally figured out that it is directly related to the rom having a built in DPI changing option in settings. All roms that have this do not work, and all that do not, work. Plus if I make extreme changes to the DPI using that setting, it is reflected a tiny bit on the head unit.
So next question... How difficult would it be to remove that built in DPI changing from one of these roms and see if that is enough to fix it???
Click to expand...
Click to collapse
You can't just "remove" it per-se. The only way is to build android yourself. Find the commit and remove it from your source and build it. Find what's linked to the dpi change and repeat process. All in all, unless you're comfortable with linux I think you're just gonna have to choose between android auto and custom roms.
exb0 said:
You can't just "remove" it per-se. The only way is to build android yourself. Find the commit and remove it from your source and build it. Find what's linked to the dpi change and repeat process. All in all, unless you're comfortable with linux I think you're just gonna have to choose between android auto and custom roms.
Click to expand...
Click to collapse
Well he listed 4 ROMs that do work so its not that black and white at least. For now, his custom ROM options may be limited but in a year or so when Android Auto compatible head units are more affordable, I'm sure there will be some devs that use it. It's just what sykopompos said, there probably isn't even a dev, at least for our phone, that has Android Auto yet. That's just because it's really new.
I don't understand how having a built-in DPI changer in the ROM is the problem though. You can simply change it in terminal on any ROM you want anyway. Just because they've built-in a GUI to change DPI, they've messed up Android Auto? Really weird.
joshm.1219 said:
Well he listed 4 ROMs that do work so its not that black and white at least. For now, his custom ROM options may be limited but in a year or so when Android Auto compatible head units are more affordable, I'm sure there will be some devs that use it. It's just what sykopompos said, there probably isn't even a dev, at least for our phone, that has Android Auto yet. That's just because it's really new.
I don't understand how having a built-in DPI changer in the ROM is the problem though. You can simply change it in terminal on any ROM you want anyway. Just because they've built-in a GUI to change DPI, they've messed up Android Auto? Really weird.
Click to expand...
Click to collapse
Exactly why I am so frustrated with it. I can run OptiPop (does not have built in DPI changing) just fine with my DPI changed to 480 (via shell) and Android Auto will display perfectly on the stereo. But the second I try and run a rom that has the baked in DPI changer (weather I have changed the dpi or not), it displays Android Auto all zoomed in as I show in my picture.
At first I thought it was AOSP/CM based roms that were the problem, but now that I have found Optipop to work correctly (AOSP based) I think that narrows it down to the DPI changer baked in. Most AOSP/CM based roms do have the built in dpi changer, which is why it took me a while to figure this out (I have pretty much flashed every rom available for the N6 haha).
I feel like if and when one of these rom devs gets android auto, it could be a fairly simple fix. Until then, I guess I am stuck finding roms that do not have the baked in dpi changer. The only one I can find currently (aside from stock based), is OptiPop.
If nothing else, hopefully my findings will help people like me in the future, and maybe even help a dev diagnose it.
joshm.1219 said:
Well he listed 4 ROMs that do work so its not that black and white at least. For now, his custom ROM options may be limited but in a year or so when Android Auto compatible head units are more affordable, I'm sure there will be some devs that use it. It's just what sykopompos said, there probably isn't even a dev, at least for our phone, that has Android Auto yet. That's just because it's really new.
I don't understand how having a built-in DPI changer in the ROM is the problem though. You can simply change it in terminal on any ROM you want anyway. Just because they've built-in a GUI to change DPI, they've messed up Android Auto? Really weird.
Click to expand...
Click to collapse
I never said that it'll never work. What I simply said was right now, at this point, he has no choice but to choose between non-dpi changing stock roms and android auto. Sure maybe in a few weeks or month someone would develop for it.
s2kpdx said:
Exactly why I am so frustrated with it. I can run OptiPop (does not have built in DPI changing) just fine with my DPI changed to 480 (via shell) and Android Auto will display perfectly on the stereo. But the second I try and run a rom that has the baked in DPI changer (weather I have changed the dpi or not), it displays Android Auto all zoomed in as I show in my picture.
At first I thought it was AOSP/CM based roms that were the problem, but now that I have found Optipop to work correctly (AOSP based) I think that narrows it down to the DPI changer baked in. Most AOSP/CM based roms do have the built in dpi changer, which is why it took me a while to figure this out (I have pretty much flashed every rom available for the N6 haha).
I feel like if and when one of these rom devs gets android auto, it could be a fairly simple fix. Until then, I guess I am stuck finding roms that do not have the baked in dpi changer. The only one I can find currently (aside from stock based), is OptiPop.
If nothing else, hopefully my findings will help people like me in the future, and maybe even help a dev diagnose it.
Click to expand...
Click to collapse
Because most of the time dpi changing isn't just a build prop modification. The last few versions of android required a little more modification to the source to make dpi changing work. If you didn't, some things might be misaligned or just wont work properly. However, I'm not sure if this is the case with lollipop. I have yet to build for it so I'm not sure, but it's just another possibility.
Lets bump this up
bump bump! this is driving me crazy! i wish i knew how to fix it
I was looking for somewhere to post this, and it seems a fitting thread. I have an app called Socializer for Meetup.com that does this same thing on my Nexus 6. It displays correctly on DirtyUnicorns and CleanROM, but not correctly on BlissPop or Euphoria. Crazy stuff. I've tried changing the DPI to no avail. Something similar to OP's problem for sure.
Seek some of these resources.
s2kpdx said:
So I have an annoyance that I wanted to see if anyone else was experiencing. I recently got a Pioneer AVIC-8100NEX head unit that has android auto built in. When I am using a stock based ROM, the android auto works fine. When I am running a CM/AOSP based ROM (with built in DPI changing), the picture is like zoomed in and is totally unusable. I can even run a stock based ROM with custom kernel and it runs just fine. I am currently running meanpop with code blue kernel and it works fine, I just miss a lot of the features of the other Roms that I can't get it to work right on.
Roms that work:
Stock
MeanPop
Sinless
CleanROM
OptiPop (AOSP based - no dpi changer)
They look like this on the head unit (how they should):
There is an Android Auto thread here at XDA, however, there are only a handful of us that have the equipment that supports it. There are several other threads outside of XDA that have information on subjects like this. So far though, there is only one developer I've found that actually owns a compatible HU.
Hopefully by the end of the year it will be more abundantly used.
Click to expand...
Click to collapse
I just got a new 4100NEX installed over the weekend and ran into exactly the same issue on Temasek's CM12.1 build. At least you've narrowed down the common thread amongst the ROMs that exhibit this issue. It saved me a lot of trial and error headache. I'm going to see if I can find the source code that references the dpi change function for one of these ROMs and see if I can figure out how to fix it. I make no promises, but it seems that our choices are drastically reduced until this issue gets resolved.
I've found that it has nothing to do with the dpi per se, but how the app scales on the ROM. Something that deviates from Stock allows the issue to occur. Ultimately the creator of the app is to blame for not setting the app to scale properly. I have only one app that acts stupid
What app are we talking about now? The one that integrates dpi scaling customization into Cyanogenmod and it's derivatives? Or Android Auto?
yes, is there a particular app on the head unit giving you trouble? I have thought of sending the dev of the app I use (Socializer) an email to see if he can nail the issue down.
i'm pretty sure the OP (and me at least) are talking about the android auto app itself
same problem really, but is there any advantage to running the ROMS that don't display properly to the ones that do?
Sent from my Nexus 6 using Tapatalk
Related
hey i know the whole OMG APPS2SD WE HAVE ROOT thing is big around here. but i dont have use for apps2sd at all. i have 14 apps and i change firmware like 9001 times a day when something new comes out. but i have 2gigs of OGG music files. and every firmware i have used ends up bugging out when im playing music and i get a notifacation with the usb headphone adapter connected. could we get a firmware optimized for music and enjoying it instead of showing off our rooted phones with no real use behind it. redirect this post if you need to. i know the whole "WRONG FORUM TOPIC LOCKED" thing happens alot here.
you can try the getting the EQ mod or the Max volume mod as well
would there be any use in me attempting to set up the sdk and pulling an all nighter to learn how to make my own NON BLEEDING EDGE but very stable release? cuz i would love to just have a stable phone with every volume thing and EQ pre installed. and that pesky sound service bug, dats gotta get fixed.
navdroid said:
would there be any use in me attempting to set up the sdk and pulling an all nighter to learn how to make my own NON BLEEDING EDGE but very stable release?
Click to expand...
Click to collapse
kinda answered your own question there didnt you?
navdroid said:
cuz i would love to just have a stable phone with every volume thing and EQ pre installed. and that pesky sound service bug, dats gotta get fixed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=517745
has preinstalled max volume, also a selection of the roms
You don't need the sdk to use the audio mods. Read a little bit more, and you will discover that you can use lucidrem's script to download the the audio mods without a pc. It takes a little patience,some time, and using the terminal. But it is easy if you follow the instructions. Also the developer of the audio mods also has several custom roms with the mods built in.
Edit. If you want a stable Rom use jf1.51, thedudes 1.2b you can add the audio mod on top of the using the bat files that comes with the audio mods
i'll try out *** - JF1.51 CRB43 US with V2 then. im used to using the terminal, its not a problem to mod my own, but being able to just quickly flash my phone back is too tempting. and @ubernicholi, i was meaning the sdk to build my own firmware as a whole. i assume its going to take me a while to understand why this whole multiple firmware bidness is a good thing, when its basicly taking all the newest unsupported code from the tree, and applying it and modifying it for the Dream handset, and in doing so, giving it 3rd party support. like downloading windows xp black pirate edition on TPB, to me its useless. ahhh the beauty of open source ^__^
why not go back to stock? it's not bleeding edge and it'll play your music just fine.
theres no shame in that.
wait. no, no...there is shame. terrible, terrible amounts of shame.
yea, but then i cant use debian. which is pretty cool so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SolemnWishing said:
Click to expand...
Click to collapse
you need to go to bed
lol I apologize I couldn't resist. So if a music centric build is what you are looking for, then it would be possible to strip out a lot of unnecessary features. First off, I think Google sync which is constantly running in the background can be taken out. Applications that are constantly refreshing, such as Mail can be removed. I understand you have apps to SD currently installed. Try internalizing the Music.apk, moving it back into the faster more reliable internal memory. Moreover, a good place to start I believe would be with the Google Ion build, which is lightning fast.
if i knew how to do that, i would slim down a stock JF update.
I think you should start out by flashing to Google Ion. Then, using ADB on your computer, enter ADB shell and being to manually remove the unnecessary applications. Whatever you don't need, take it out. As for Google sync, go to settings and disable it. Also in settings, disable notifications. At a point, you can even just turn off the radio and switch to airplane mode. That way no other services are running and you can listen to music uninterrupted, at the cost of not being able to accept calls.
wow, thanks for the support. i was looking at ION and thinking that it would be perfect. but im not really sure how to set up the development on fedora 11.
navdroid said:
wow, thanks for the support. i was looking at ION and thinking that it would be perfect. but im not really sure how to set up the development on fedora 11.
Click to expand...
Click to collapse
Ion FTW.
You set it up the same as you do on any other distro...
and...
what do you honestly do with debian on your phone?
As in on your computer? Are you running Linux or any operating system based on Linux? If so, unfortunately I can't help you there, I mostly use Windows and occasionally Wubi ):
(In all honesty I have very little knowledge when it comes to running Linux on a computer, so sorry about that haha)
I forgot to add, maybe increase your processor clock speed to 528Mhz. Look for an app called SetCPU. It is here on the forums for free, as the creator is among us or alternatively download it from the market, however it is a paid app on their.
if u use ion use R1 its faster than R2 in my opinion
i use um that overclock widget, i love that thing, works so well. umm. debian on my phone is pretty cool. it has potential. umm i might set this up and get a small release with just my name and roadmap on it.
navdroid said:
i use um that overclock widget, i love that thing, works so well. umm. debian on my phone is pretty cool. it has potential. umm i might set this up and get a small release with just my name and roadmap on it.
Click to expand...
Click to collapse
Hmm.. looking at your signature, overclocking your PC, and even getting Debian to work in the first place, I think you are definitely capable and very experienced. Best of luck to you
Let us know if you are able to get that stripped down version of Google Ion working. I would do it, but I don't know how to resign updates and I just finally settled down on Haykuro 6.0.1 after a ROM struggle between JAC's Hero, TwistedUmbrella's Hero and JF1.51 where I was flashing a new ROM on a daily basis.
my only thing is my work ethic and lack of programming experiance. if anyone could help me get started. hell, i might actually post something in the android development outlining the project goals and stuff like that.
See http://forum.xda-developers.com/showpost.php?p=11470392&postcount=98 for the reason why I discontinued development.
Simpfinity 1.6
Short blurb:
Simpfinity is a ROM aimed at Canadians, by a Canadian (but not only for Canadians!). It's simple, elegant, and a powerhouse if you want it to be.
Changelog
1.6
Removed more unnecessary system APKs
Updated SuckerPunch Kernel
Changed to KP1 modem
1.55
Removed SMS from call log
Added Voice Search by default
Tweaked puzzle lock screen
1.5
Removed the TouchWiz launcher, as it was draining battery like crazy, even when not being used. This means:
Bettery battery life!
Added LauncherPro as the default launcher
Removed Samsung Keyboard
Added themed Gingerbread Keyboard
Fresh install required, no update will be given to this version
1.01
Removed flash player being installed by default since it can be installed from the market
Removed the TouchWiz Wallpaper chooser
Removed the TouchWiz Live Wallpapers
Removed other junk
Base Stats:
Rogers Froyo 2.2 JL1-based
SuckerPunch-SmR #40 1400MHz 100-Hz OC/UV Kernel
KP1 Modem
Features:
Removed Rogers Bloat
Removed Samsung Bloat
Large APN List
Updated Google Apps
Blue Circle Battery Mod
Any other stock Rogers JL1 features, such as the 4 touch buttons lighting up when the screen is pressed
Faster Window Transitions/Animations
Lockscreen sounds enabled by default
ThinkFree Office is installed as a regular app, so it can be easily uninstalled if you do not want it
Kernel Features:
Android 2.2.1 JPX Source
Works on all stock Froyo 2.2 and 2.2.1 ROMs and popular custom ROMs
Hardcores Speedmod K12P Patch
Supercurios Voodoo Sound v3
Hardcores Brightness Fix
Includes Neldar's Backlight Notification
339MB RAM and all features should work
Uses CFQ I/O Scheduler by Default
Includes Hardcores Startup Speed Tweaks
Properly working TinyRCU Patch
Patched lowmemorykiller
OC up to 1280mhz
UV Support using Voltage Control App
Includes hpcall support
IPv6 Privacy Extensions enabled
More information on the kernel available here.
Added apps:
Voltage Control 3.0
Voodoo Control App 0.4
SGS Kernel Flasher
Spare Parts
Galaxy Tuner
AOSP News and Weather App/Widget
Known Issues:
Bluetooth headset static *see bottom of post for a workaround*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks To:
UOT Kitchen for providing the PNG's that made the battery mod possible
MikeyMike01
Mammon88 for the call log fix
chrisryn
existz for the kernel
This ROM has been tested by me for several days now and works awesome from my testing.
Installation:
Copy the zip to your sdcard, reboot into recovery, and flash! The updater script should take care of all needed wiping, so unless you have a lagfix that isn't supported by SuckerPunch, you shouldn't have to do anything but flash. If you're on a stock ROM with 3e recovery, please read this.
Note: I'm not sure if the lagfix and tweaks are enabled by default, so after installing go into recovery and check. If they're not, enable the recommended tweaks and enable the lagfix if so desired! If you're coming from stock let me know what happens so I can update this section.
Also, if you experience charge death please read the kernel thread.
Warning: Just like every other ROM, you flash at your own risk. If my ROM somehow blows up your phone, makes your phone do a flying dragon kick to your face, or makes your girlfriend leave you for me, I will not be held responsible.
Download!
Simpfinity 1.6
Simpfinity 1.55
Simpfinity 1.5
Simpfinity 1.0
Simpfinity 1.5 to 1.55
Simpfinity 1.0 to 1.01
If you want bluetooth calling support you unfortunately have to use the stock kernel and modem for the moment, however you can still have voodoo! Just flash this, courtesy of s44.
I gotta try this tonight! thanks!!
by the way I should disable voodoo first before flashing if im coming from cognition correct?
ckelvin87 said:
I gotta try this tonight! thanks!!
by the way I should disable voodoo first before flashing if im coming from cognition correct?
Click to expand...
Click to collapse
If your partitions are EXT4, you shouldn't have to disable voodoo, but it can't hurt.
How's this on battery?
What are your Undervolt settings?
Any bugs that you know of?
Any other random information I might need to know?
crecsky said:
How's this on battery?
What are your Undervolt settings?
Any bugs that you know of?
Any other random information I might need to know?
Click to expand...
Click to collapse
I find battery life to be similar to just about every other ROM out there. The most important factor in battery life is the kernel, and when undervolted SuckerPunch is fantastic on the battery. From what I can tell 30+ hours should be possible with moderate usage.
I'm a battery life whore, so I personally do not overclock unless I need it for a specific app (Like a PSX emulator for example). My 1000MHz UV settings from low to high are as follows:
-150,-150,-150,-125,-125 - I haven't experienced a crash yet with these settings, but remember that every phone is different and what works for me may not work for you.
I'm not aware of any bugs, but let me know if you find any! I'm not amazing like MikeyMike01, designgears, the Phoenix/Firefly team, the Andromeda team or many others, but I'll do my best. There shouldn't be any bugs that aren't present in the stock ROM, but it's possible I messed something up.
Not really sure on any other random information, but you might want to consider using APN Backup and Restore to backup your APN's, just in case my list doesn't work for you for whatever reason.
Why did people rate this 3 stars? Trolls, looks good btw
Nickel Dime Bay said:
Why did people rate this 3 stars? Trolls, looks good btw
Click to expand...
Click to collapse
Thank you
I'm not sure why. Someone rated it 1 star before there were even any replies.
I like the blue Battery.
what all customizations did you do for the screen shot?
rockosifraldi said:
I like the blue Battery.
what all customizations did you do for the screen shot?
Click to expand...
Click to collapse
Just LauncherPro and the background. Nothing else is changed from the stock ROM. If there's interest I can definitely post up the wallpaper.
It's all good. Just wanted to know.
I've got a Rogers Captivate and I live in Calgary, so I should be good.
I'm giving it a go so I'll let you know.
And with the Voltage Control, when it crashes the phone is still on and can receive messages and stuff but the power button doesn't turn the screen on right? It's happened to me a couple times on other roms and I'm just trying to figure out if it because of bad settings I have.
crecsky said:
It's all good. Just wanted to know.
I've got a Rogers Captivate and I live in Calgary, so I should be good.
I'm giving it a go so I'll let you know.
And with the Voltage Control, when it crashes the phone is still on and can receive messages and stuff but the power button doesn't turn the screen on right? It's happened to me a couple times on other roms and I'm just trying to figure out if it because of bad settings I have.
Click to expand...
Click to collapse
That's one way for it to crash, yeah. The most common way though is for it to hard-lock during use, ending up with you having to pull the battery to reboot.
How is this Canadian? ie how does it differ from the americanized versions? What was not changed to keep it canadian?
I support all your hard work and I'm looking forward to a canadian version but it just looks like rogers rom minus samsung/rogers bloat with a new kernel +APN backup and restore +a few apps...
unless I'm missing something
disellusional said:
How is this Canadian? ie how does it differ from the americanized versions? What was not changed to keep it canadian?
I support all your hard work and I'm looking forward to a canadian version but it just looks like rogers rom minus samsung/rogers bloat with a new kernel +APN backup and restore +a few apps...
unless I'm missing something
Click to expand...
Click to collapse
That's basically what it is, plus the battery mod, a few settings tweaks, as well as a better kernel and modem. What makes it Canadian is the Rogers ROM itself. The other Rogers ROMs here are Americanized, whereas mine is not.
The Locale is English (Canada) rather than English (US), and the stock keyboard has Canadian spellings of words as well as the American ones (though if the Canadian spellings are removed from the other ROMs I do not know). The default time and date format is also day/month/year, rather than month/day/year.
There aren't a ton of differences between my ROM and say Cognition 3.04, but I spent a lot of time tweaking the stock ROM to my liking, and even longer packaging it into something installable, because I figure there's other people out there who would like it as well. If a single person uses my ROM and likes it, I'm happy with that.
good job mate. I will try this weekend.
GPS should be okay as well I presume.
Great Canadian ROM, EH?! I will try this out tonight. Yes, great to have Canadian locale built into Rogers Froyo. Thx.
shawn122 said:
good job mate. I will try this weekend.
GPS should be okay as well I presume.
Click to expand...
Click to collapse
From my testing, GPS seems to work fine. I can get a lock in my basement even, if I try really hard.
Auridran said:
From my testing, GPS seems to work fine. I can get a lock in my basement even, if I try really hard.
Click to expand...
Click to collapse
Holy crap! You have to be running a GPS extension through a window or something. I can't even do that! Great job though. I may adjust the locale and play with this for the heck of it.
Have you changed any of the GPS files in this ROM?
I assuming from your original post that all you did was trim fat and left the Rogers stock in check? If so I'll definitely install this.
If haven't already, ive been using the combo of:
- Stock Rogers 2.2 ROM
- SuckerPunch (or SpeedMod) Kernel
- KP1 Modem
Quite honestly i've had better results than with the JK4 to me in terms of GPS. Instant locks and tracking in Toronto. As long as you leave the Rogers stock ROM unchanged and don't use the "GPS fixes" to alter it.
The only features i really think need to be added to the stock Rogers ROM are the Gingerbread Keyboard (which gives you voice input that doesn't come stock ), an accurate battery mod and the extended power menu (to give you the reboot features).
Anyway, if you feel like trying it out for the next version of this ROM I highly recommend it.
Auridran said:
Simpfinity 1.0
The updater script should take care of all needed wiping, so unless you have a lagfix that isn't supported by SuckerPunch, you shouldn't have to do anything but flash.
Click to expand...
Click to collapse
Wait wait
Does that mean the script is going to WIPE my internal SD?
I plan to flash this without wiping my internal SD because it's got pictures and lots of other ROMs and tweak zips and such and I am at work and do NOT want to backup my entire SD...
Please clarify, and thanks!
adamholden85 said:
Holy crap! You have to be running a GPS extension through a window or something. I can't even do that! Great job though. I may adjust the locale and play with this for the heck of it.
Click to expand...
Click to collapse
Haha yeah, I honestly don't know how I did it, but it happened! I tested the GPS outside today and got 9 satellites in about 9 seconds.
sniperIT said:
Have you changed any of the GPS files in this ROM?
I assuming from your original post that all you did was trim fat and left the Rogers stock in check? If so I'll definitely install this.
If haven't already, ive been using the combo of:
- Stock Rogers 2.2 ROM
- SuckerPunch (or SpeedMod) Kernel
- KP1 Modem
Quite honestly i've had better results than with the JK4 to me in terms of GPS. Instant locks and tracking in Toronto. As long as you leave the Rogers stock ROM unchanged and don't use the "GPS fixes" to alter it.
The only features i really think need to be added to the stock Rogers ROM are the Gingerbread Keyboard (which gives you voice input that doesn't come stock ), an accurate battery mod and the extended power menu (to give you the reboot features).
Anyway, if you feel like trying it out for the next version of this ROM I highly recommend it.
Click to expand...
Click to collapse
Try what out? Do you mean the Extended Power Menu or KP1? And no, there are no "GPS fixes" - I don't find them necessary.
kppanic said:
Wait wait
Does that mean the script is going to WIPE my internal SD?
I plan to flash this without wiping my internal SD because it's got pictures and lots of other ROMs and tweak zips and such and I am at work and do NOT want to backup my entire SD...
Please clarify, and thanks!
Click to expand...
Click to collapse
No it won't wipe your internal SD. It only wipes your System/Data/Datadata/Cache, and a couple other things like all other ROMs.
Searched for this, and found CM6 speed test results, but none for CM7 and if the kernels are different, options can be different, so results can be different.
I've tried various ROMs since CM dropped official G1 support, and they're all very similar, but I needed somewhere to document the settings that work best for me.
I only use Quadrant for my benchmarking. I feel it's well-rounded in its tests, it's free, and I get a seemingly completely arbitrary number at the end.
The best Quadrant score I can recall getting was 373, although I can't help but think I once got in the low 400s. I do remember trying every trick I could to get it into the low 300s, but I'm consistently getting 360's and peaking at low 370s with the current setup.
I'm currently running FireRat's CM7 Magpie, version 2011-09-26, which is only one version behind his latest as of this posting. I am running ADW Launcher as downloaded from market (because I like how its menu entries are arranged better -- that's the only reason). I have only 2 screens, and really don't even need that many.
Performance Settings Adjustments:
MENU / SETTINGS / CYANOGENMOD SETTINGS /
Code:
PERFORMANCE
CPU
ONDEMAND, 176, 614, Restore on boot=Yes
Compcache - 18% (Default)
NO JIT
NO DITHERING
YES PURGING OF ASSETS
NO MEMORY LOCKS
VM Heap=24m (default?)
My Micro-SD is a class 4, 4GB. Partitioned [*FAT32][~350M Ext4][64M Swap]
and I'm not using the swap partition AFAIK.
Non-performance settings adjustments:
(Really, I doubt any of these have much effect if any at all on performance)
Code:
Menu/Settings
CyanogenMod Settings
Application
*All left at defaults
Display
All unchecked except 0 and 90 degrees rotations
Input
Only change was long-press home, set to show 12 screens.
Interface
Edited my power widget to my liking. Doubt it has any effect on speed.
Status Bar Tweaks
Checked: All except Status Bar Brightness.
AM/PM set to small, Alternate Signal left at default (bars)
*Everything else in "Interface" left at defaults.
Lockscreen
Disable - unchecked
Style Options - Ring, Ring, Custom App Starter, added Camera, default background
Widget Options
Always display battery
Centered
No to the Music
Next Calendar (doesn't seem to work)
--All Calendars selected
--Reminders-Only not checked.
--Lookahead 3 days.
Unlock options -- All left at defaults (all unchecked)
No to the Gestures.
Finally, in MENU/Settings/Applications/Preferred Install Location, SD EXT is selected. In Applications/Development, USB Debugging is on (disabling it did not speed things up any) and stop-via-long-press is disabled (probably no effect).
I *am* running a theme, but since a theme is mainly just picture swaps (I think?) it shouldn't affect much. I'm running GlassMix. Not the coolest, but not bad at all. I rather like it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to reply with your best quadrant score and settings that got it -- preferably on the same ROM but other CM7-based ROMs would be welcome comparisons...
The first ,i learn,thanks
Getting a quadrant score of 393 with 2.3.5 GRP CM7, overclock to 614 MHz, purging of assets on, and the disabling verify-bytecode hack. Fastest I have seen on a g1! I get 369 with normal CPU clock.
slowpoke88 said:
Getting a quadrant score of 393 with 2.3.5 GRP CM7, overclock to 614 MHz, purging of assets on, and the disabling verify-bytecode hack. Fastest I have seen on a g1! I get 369 with normal CPU clock.
Click to expand...
Click to collapse
Might have to try this ROM out. When it first showed up, it seemed to be little more than a compilation direct from CM7 and AOSP sources, which of course anyone who can follow a HOWTO can do themselves... and many have. Back then, I felt this guy was just one more of those guys. I wasn't convinced he really had any developing experience before starting with it, and I really wasn't impressed with him personally, based on comments he made in several threads -- particularly against a known (if sometimes disliked) developer who has contributed a decent amount to the community. I'll have to go back and see what all has been done recently in this ROM if its performance is consistently good enough that the hack you mentioned worked so well (it made no difference on the CM7-Magpie I'm running).
EDIT: Nevermind, turns out I didn't know who I was talking about.. actually, I did know who I was talking about, it just turned out he was someone other than the person who actually started GRP so nevermind all this (read next two posts)...
cj chitwood said:
Might have to try this ROM out. When it first showed up, it seemed to be little more than a compilation direct from CM7 and AOSP sources, which of course anyone who can follow a HOWTO can do themselves... and many have. Back then, I felt this guy was just one more of those guys. I wasn't convinced he really had any developing experience before starting with it, and I really wasn't impressed with him personally, based on comments he made in several threads -- particularly against a known (if sometimes disliked) developer who has contributed a decent amount to the community. I'll have to go back and see what all has been done recently in this ROM if its performance is consistently good enough that the hack you mentioned worked so well (it made no difference on the CM7-Magpie I'm running).
Click to expand...
Click to collapse
The guy who made that rom was jbirdvegas, before he made it to the cyanogenmod team. If he made it into cyanogenmod team, he must have known what he was doing.
Sent from my Froyo on Dream/Sapphire using Tapatalk
maximo360 said:
The guy who made that rom was jbirdvegas, before he made it to the cyanogenmod team. If he made it into cyanogenmod team, he must have known what he was doing.
Sent from my Froyo on Dream/Sapphire using Tapatalk
Click to expand...
Click to collapse
Oh, okay, then forget my last statement cus I was under the impression it was someone else entirely... maybe someone was going to make their own and started with GRP as a base... but the way I read this guy's posts, it looked like _he_ started GRP. Thanks for the clarification (I probably could have found this out if I had taken time to research the ROM, come to think of it... () )
i get 360s too
cj chitwood said:
Oh, okay, then forget my last statement cus I was under the impression it was someone else entirely... maybe someone was going to make their own and started with GRP as a base... but the way I read this guy's posts, it looked like _he_ started GRP. Thanks for the clarification (I probably could have found this out if I had taken time to research the ROM, come to think of it... () )
Click to expand...
Click to collapse
Its ok, i know why, you must think dw9906 made the rom, but he was just building the rom and posting it here because jbird gave him consent to do so since he was going to be unable to continue the rom since he was accepted to the CyanogenMod team. I'm not sure if he started GRP by himself, I think it was a couple of people who started it.
Also, i have one question for you, which rom FEELS faster for you, Cyanogenmod 7 Magpie, or ADS Magpie?
I noticed you used to run ADS Magpie and are now running CM 7 Magpie, and I'm just curious to know why.
Good info!!!!!!!!!!!!!!!!
maximo360 said:
Its ok, i know why, you must think dw9906 made the rom, but he was just building the rom and posting it here because jbird gave him consent to do so since he was going to be unable to continue the rom since he was accepted to the CyanogenMod team. I'm not sure if he started GRP by himself, I think it was a couple of people who started it.
Also, i have one question for you, which rom FEELS faster for you, Cyanogenmod 7 Magpie, or ADS Magpie?
I noticed you used to run ADS Magpie and are now running CM 7 Magpie, and I'm just curious to know why.
Click to expand...
Click to collapse
Uhm, honestly, they do FEEL about the same, which is why speed isn't the biggest concern for me. BOTH of them get laggy at times, and by laggy I mean two things
1) Sometimes scrolling through my apps drawer is blocky (not smooth).
2) Sometimes apps take a while to open, or, simply to do things.
Usually, 1) happens more frequently, but it doesn't bother me as my phone's doing a LOT of things.
2) However, doesn't happen that often on either ROM. However, when it happens, it's always after I've been running several different programs, especially maps with GPS enabled.
Usually, I have most of my phone turned off, so GPS, 3G, rotation, none of that comes into play in the list of things my phone is doing. If I had them running all the time, I'd be on FroYo or Eclair, not Gingerbread. The phone couldn't handle it. Or, I couldn't handle the phone.
In the end, the two are largely the same for me. The main reason I chose Firerat's over And DiSa's is that the Firerat ROM has CPU government built-in, where I have to have a CPU setting utility with ADS. Also, there was some thing or two else that Firerat/CM7 have built-in that ADS/ezGingerbread do not. Maybe the sound equalizer? Not that I run that too often, but it's nice to have.
EDIT: And you're right, I thought it was DW. Plus, you explained there why it must have seemed that DW just picked up someone else's work... he did! but I know now why, and I was missing that info before, so thanks again... Still didn't care for the interaction 'tween him and Firerat but that was something else (and yeah, FR isn't the easiest to get along with but I tend to let peoples' personalities just kinda slide -- usually -- especially in a text forum where tonal variations aren't heard ).
Damn, 311 using froyoByLaszlo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Smooth like Butta
Follow on G+: Team Vanir
Vanir Team:
NuclearMistake
Sonicxml
DHO
PrimeDirective
Not all features are available yet.
Features:
Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android with subtly improved versions of the features you love to as many devices as possible. we've tried to incorporate and improve our features in a way that makes them more cohesive to improve the overall user experience while correcting any performance regressions and improving functionality..
What to expect:
- This is not a McCopy ROM. What goes into our build is well thought-out and not a bunch of stuff duck taped together because we could.
- maximum optimization. We do our research. We test hard. We build -fstrict -O3 globally and include a massive array of code optimizations and memory leak fixes that we write ourselves and eventually submit to AOSP or Linaro.
- originality in our source. We generate a lot of new commits being features or general code improvements. We are open source to share and improve the community but we also try to make sure we offer a unique experience.
- aesthetics.. hopefully in your opinion
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
UI and graphics improvements
custom navbar, navring, and hardware key features
improved notification handling (active display & halo are in review also)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
yatta yatta yatta
more to come when i feel like updating the op
Changelog:
**Vanir Open Status
**Vanir Merged Status
Vanir Downloads (nuclearmistake):
**Nightlies
Recovery Downloads:
**TWRP 2.7
**CWM
Vanir Github:
**VanirAOSP Git
Gapps:
**4.4.2 PA Gapps
Installation Instructions
Make sure your using twrp above it's required
Full wipe
Install ROM
Install Gapps
Thanks
TeamVanir
Meticulus
Everyone here for keeping me inspired
Too many to thank. You know who you are who stood by since day 1
Reserved
Awesome Job Unjustified Dev! Another New Great ROM to add to the list. It's definitely smooth like butter! Thank you!
Sent from my SGH-T599X using XDA Premium 4 mobile app
Thanks for this ROM which someone can fix the BT audio in call but thanks I will use this one I like thanks again
Sent from my SGH-T599N using xda app-developers app
Tethering
Nice to see a few ROMs for the T599! I am testing on the T599 T-Mobile variant.
Maybe there is an issue with Bluetooth.
Bluetooth tethering is not working.
But, WiFi tethering is working fine. :good:
Installed smoothly once I updated CWM. Will post on how it goes from here.
ps That's a bad ass boot image lol
Edit: Not a fan of how you put Vanir over the space bar, but I guess it doesn't matter because I'm not going to be using the stock keyboard anyway.
Edit2: Phone seemed to turn off randomly in the middle of the night, other than that it's working great so far.
Edit3: The music app combined with DSP Manager is pretty neat. If the music is distorting, the music app will pause to avoid damaging your system.
Edit4: Screen recording completely freezes the phone.
Kennehisftw said:
Installed smoothly once I updated CWM. Will post on how it goes from here.
ps That's a bad ass boot image lol
Edit: Not a fan of how you put Vanir over the space bar, but I guess it doesn't matter because I'm not going to be using the stock keyboard anyway.
Edit2: Phone seemed to turn off randomly in the middle of the night, other than that it's working great so far.
Edit3: The music app combined with DSP Manager is pretty neat. If the music is distorting, the music app will pause to avoid damaging your system.
Edit4: Screen recording completely freezes the phone.
Click to expand...
Click to collapse
Screen recording doesn't work on these devices. I am removing the option that shows that to prevent device freezing.
I've redone the device tree and device is now codinalte. I made this change so that the assert checks won't allow flashing of older recoveries which would lead to device bootloops if used with the new j4fs and param setup.
Make sure you see the new instructions.
Changelog
-Used gcc 4.8 instead of 4.7 now that it's been tested.
-Removed all device asserts to prevent use of older recoveries.
-Disabled the use of screen record
-Switched device name to codinalte to cause less confusion with ace 2 users
-Upstream Vanir changes
-Philz cwm , cwm , and twrp now available for codinalte enabled builds only
Excellent ROM
Sent from my SGH-T599N using XDA Premium 4 mobile app
To everyone wondering this is the initial release of codinalte. I made this change to ensure everyone would be on the correct recovery and if you are on an older one it wouldn't let you install it . It would cause a bootloop due to the mismatch of j4fs and param module. This is the only way I can think of to ensure everyone is safe.
Unjustified Dev said:
To everyone wondering this is the initial release of codinalte. I made this change to ensure everyone would be on the correct recovery and if you are on an older one it wouldn't let you install it . It would cause a bootloop due to the mismatch of j4fs and param module. This is the only way I can think of to ensure everyone is safe.
Click to expand...
Click to collapse
What bugs does this have other than the Bluetooth audio? Same as Omni Rom?
Cogra147 said:
What bugs does this have other than the Bluetooth audio? Same as Omni Rom?
Click to expand...
Click to collapse
Yes , we should all have the same bugs. The only ones that will make a difference are rom specific issues.
Unjustified Dev said:
Yes , we should all have the same bugs. The only ones that will make a difference are rom specific issues.
Click to expand...
Click to collapse
Here are some bugs I'd experienced recently with VanirAOSP ROM latest build.
1. Last night I had set my alarm clock to wake up this morning but the alarm didn't go off because I found my phone shutdown or powered off. Apparently the randomly shutdown in the middle of the night.
2. Yesterday I had two occasions where my Network was lost completely. I had to reboot the phone to get it back.
3. I noticed that when I receive a call or make a call the volume sounds like is half way down. I always have my volume set all the way up. When someone calls me I have to hit the volume down one or twice and then back up to fix the loudness of the call. Something is not right.
4. I noticed that when ever I play and embedded YouTube Video whether in a Browser of any kind or an RSS Reader it FCs the application before the video starts. All the time. Here is an example. I recorder this LogCat for you....https://www.dropbox.com/s/aaf7wgywrf66b7a/2014-03-17-14-15-24.txt I try playing a YouTube video on this website.. http://sploid.gizmodo.com/here-are-7-facts-about-superheroes-you-probably-didnt-1541767101 on the AOSP Browser and same thing happens with other Browsers and apps with YouTube Video embedded in them.
Sent from my SGH-T599N using XDA Premium 4 mobile app
DJVargas said:
Here are some bugs I'd experienced recently with VanirAOSP ROM latest build.
1. Last night I had set my alarm clock to wake up this morning but the alarm didn't go off because I found my phone shutdown or powered off. Apparently the randomly shutdown in the middle of the night.
2. Yesterday I had two occasions where my Network was lost completely. I had to reboot the phone to get it back.
3. I noticed that when I receive a call or make a call the volume sounds like is half way down. I always have my volume set all the way up. When someone calls me I have to hit the volume down one or twice and then back up to fix the loudness of the call. Something is not right.
4. I noticed that when ever I play and embedded YouTube Video whether in a Browser of any kind or an RSS Reader it FCs the application before the video starts. All the time. Here is an example. I recorder this LogCat for you....https://www.dropbox.com/s/aaf7wgywrf66b7a/2014-03-17-14-15-24.txt I try playing a YouTube video on this website.. http://sploid.gizmodo.com/here-are-7-facts-about-superheroes-you-probably-didnt-1541767101 on the AOSP Browser and same thing happens with other Browsers and apps with YouTube Video embedded in them.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could try this for low call fix http://forum.xda-developers.com/showthread.php?t=2676518
Use the onlyincallfix.apk it should work to fix volume please confirm this.
The video problem is due to the patches we used not supporting a certain function required for the video playing. The phone randomly dying is something i know nothing about as of yet.
Does it work on the international version and does it have random reboots like in the latest CM11?
LMH1998 said:
Does it work on the international version and does it have random reboots like in the latest CM11?
Click to expand...
Click to collapse
This is not for s3 mini. Please wait some time for me do a test build. I don't have the s3 mini but it's a similar device. If you want I can send you a pm of the test build. Please continue this conversation in a private message.
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
wilbigdaddy2000 said:
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
Click to expand...
Click to collapse
I am looking into it. I haven't noticed why it did that yet. I can add back dvfs limit if you think it's the voltage. Basically you won't be able to use performance control it will stay at 0 for min and max.
Unjustified Dev said:
I am looking into it. I haven't noticed why it did that yet. I can add back dvfs limit if you think it's the voltage. Basically you won't be able to use performance control it will stay at 0 for min and max.
Click to expand...
Click to collapse
wilbigdaddy2000 said:
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
Click to expand...
Click to collapse
The same thing happened to me, but while running Beanstalk. I have been running Vanir for the past few days and I have not seen any issues with FC or reboot yet. Battery life appears to be excellent, lasting 48 + hours with light use.
I am running the T-Mobile variant.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. This version comes in two flavors, GMS and vanilla. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Here
Extra features:
MindTheGapps included
3 finger swipe screenshot
NoName (4.14.314) kernel included
Stock-like FOD implementation
Signature spoofing patches
Download
GMS
Vanilla
Lineage Recovery
If you like my work consider supporting me:
Ko-Fi
Notes
Core google apps are pre-included in the GMS variant, hence it isn't needed to flash them on-top
Lineage Recovery included
Android 11 firmware Based
Android OS version: 13
Security patch level: May 2023
Build author/Device Maintainer: Skyblueborb
Support Group: Here
Device Source code: Here
Vendor Source code: Here
Kernel Source code: Here
Source code: https://github.com/LineageOS
RESERVED
Changelod 05.05.2023:
• Updated to May ASB
• Introduced network traffic indicator
• Improved system smoothness on default kernel
• Improved UDFPS latency
Thanks friend. Just what I ve ben waiting for.
This looks tasty!
Two Questions:
(A) Is it possible to upgrade from your other LineageOS 18.1 Rom, or is a clean install required?
(B) I do a lot of long exposure pictures and therefore use the pro mode on the stock camera app quite often. Is it included again? (The camera app in LineageOS was always very limited years ago, I don't know how it is now.)
Typhoon_Master said:
This looks tasty!
Two Questions:
(A) Is it possible to upgrade from your other LineageOS 18.1 Rom, or is a clean install required?
(B) I do a lot of long exposure pictures and therefore use the pro mode on the stock camera app quite often. Is it included again? (The camera app in LineageOS was always very limited years ago, I don't know how it is now.)
Click to expand...
Click to collapse
A) you can't dirty flash, clean flash required
B) the stock cam is not included, but the aperture camera lineage 20 comes with is really great, not sure about long exposure shots tho, probably some gcam would suit that need nicely
Skyblueborb said:
RESERVED
Click to expand...
Click to collapse
Hi,
I installed your rom on my Mi A3 European model.
Since one week, everything went well, and overall everything works fine except:
- SMS won't send if LTE call are activate (I use google message app)
- Battery decreases when I use android auto in my car (connected on USB) whereas before (A11 xiaomi stock rom) my phone was charging
- The "night filter lighting" is too much yellow even when setting it to the minimum (0% now is ~30% before on A11 xiaomi stock rom)
- The automatic brightness works badly (I had to use macrodroid to manage this setting)
Otherwise thank you very much for your work, everything else works perfectly for the moment. It's the first time I use lineageos on my phone, how will it be for updates? (OTA or manually?)
Hobbi1 said:
Hi,
I installed your rom on my Mi A3 European model.
Since one week, everything went well, and overall everything works fine except:
- SMS won't send if LTE call are activate (I use google message app)
- Battery decreases when I use android auto in my car (connected on USB) whereas before (A11 xiaomi stock rom) my phone was charging
- The "night filter lighting" is too much yellow even when setting it to the minimum (0% now is ~30% before on A11 xiaomi stock rom)
- The automatic brightness works badly (I had to use macrodroid to manage this setting)
Otherwise thank you very much for your work, everything else works perfectly for the moment. It's the first time I use lineageos on my phone, how will it be for updates? (OTA or manually?)
Click to expand...
Click to collapse
1st and 2nd issues i haven't encountered (i don't have android auto easily accessible to test), night light can somewhat be tuned manually via the live display color calibration, auto brightness is tuned to your usage, if you have it enabled try nudging the bar to how you like it, after a while it will follow the preferences you set.
I might implement OTA, but that would still require at least one manual upgrade
Glad you enjoy the rom
Thanks a lot for the rom. Everything works perfect out of the box. I did a clean install coming from your lineageos 18 build. The new lineageos camera app is really good. I could easily install microG and universal safetynet fix. If we can't find updates here, I'll take a look at your telegram channel OTA would be a great solution to this.
Any chance of trying to go official? The immediate advantage would be the automated (weekly) builds, with free OTA upgrades, and fixes from the upstream devs when they break things on their side.
Skyblueborb said:
1st and 2nd issues i haven't encountered (i don't have android auto easily accessible to test), night light can somewhat be tuned manually via the live display color calibration, auto brightness is tuned to your usage, if you have it enabled try nudging the bar to how you like it, after a while it will follow the preferences you set.
I might implement OTA, but that would still require at least one manual upgrade
Glad you enjoy the rom
Click to expand...
Click to collapse
Hi,
For Android Auto, I tried with another USB cable and it charges correctly during use. It's strange the USB cable I had, worked perfectly for 2 years, I tried it again after android auto update and the phone still discharges but less... I think it comes from android Auto updates more than your rom.
Now I'm looking to recover the stock camera app from the mi A3 which allows the use of wide angle, the 48Mpx sensor and saving directy on SD card.
Anyone tried ANXCamera?
Can you release a version without the GAPPS ?
Or at least with the minimal Pico variant?
There are people who really dislike to see google everywhere and prefer to use devices that are out of the scope of constant surveillance and some of them prefer using LOS exactly with that idea in mind.
enapah said:
Any chance of trying to go official? The immediate advantage would be the automated (weekly) builds, with free OTA upgrades, and fixes from the upstream devs when they break things on their side.
Click to expand...
Click to collapse
There are several problems with official, the source modifications i made aren't allowed in official (without them performance would be slower, FOD would be blinding, just to name a few)
nov01 said:
Can you release a version without the GAPPS ?
Or at least with the minimal Pico variant?
There are people who really dislike to see google everywhere and prefer to use devices that are out of the scope of constant surveillance and some of them prefer using LOS exactly with that idea in mind.
Click to expand...
Click to collapse
Please read the post again, especially the download section, the vanilla version is available, and the gms variant is (as it states in the notes) only core Gapps (playstore and play services)
Skyblueborb said:
There are several problems with official, the source modifications i made aren't allowed in official (without them performance would be slower, FOD would be blinding, just to name a few)
Click to expand...
Click to collapse
Thanks for your time
Edit (quick reply posted prematurely on line change, sorry): Because you already build two different versions (GMS and vanilla) maybe it would be feasible to have the "less than ideal but well supported" official version while still keeping the "optimized and overall better" fork? Just spitballing here, I am fully aware of the hurdles the device charter creates -- incidentally, those that make it through the process usually end-up being well supported all-around.
I second that, that would be wonderful. People are so disappointed by Xiaomi about the A3. A nice device with great hardware but abandoned early by Xiami and the community and lots of problems during its official life span.
enapah said:
Thanks for your time
Edit (quick reply posted prematurely on line change, sorry): Because you already build two different versions (GMS and vanilla) maybe it would be feasible to have the "less than ideal but well supported" official version while still keeping the "optimized and overall better" fork? Just spitballing here, I am fully aware of the hurdles the device charter creates -- incidentally, those that make it through the process usually end-up being well supported all-around.
Click to expand...
Click to collapse
I thought long and hard about applying for official, but in the end i didn't think it would succeed, there are a plethora of different officially supported roms for A3 which would all perform better than Lineage official, and i feel that official is really limiting what i can do. About mainting two versions, yes i do, theoretically even 4 versions (GMS/Vanilla for Los 18/20), but official also needs a lot of attention, they require you to spend time on it, and that would mean it would eat more of my time, doing a thing i do not believe will succeed (maybe the fod can be fixed, but geekbench scores and others cannot be easily fixed from the device tree alone)
And what do you mean about the good all-round support? Getting regular updates?
The whole device tree and vendor passes the device requirements afaik, but i don't wanna release a build with FOD that doesn't have dimming, it would really make the build failed in my eyes.
Hey thank you for this great ROM, I really love it, it has much better functionality then stock. I like the adb root feature. Of course official would be nice, but I understand your decision.
I am having only one issue: When calling with headset via audio jack the volume is way to high even on the lowest setting. Is there any way to change this? Couldn't find a proper way to adjust that.
Thank you for a reply
MeatHill said:
Hey thank you for this great ROM, I really love it, it has much better functionality then stock. I like the adb root feature. Of course official would be nice, but I understand your decision.
I am having only one issue: When calling with headset via audio jack the volume is way to high even on the lowest setting. Is there any way to change this? Couldn't find a proper way to adjust that.
Thank you for a reply
Click to expand...
Click to collapse
The volume of the mic, or the volume of what you hear?
Hey, I am interested in installing this on my Xiaomi MI A3. Does it support adding a work profile/account? This is a feature that I use on my stock rom and it is essential. Thanks
Eleari said:
Hey, I am interested in installing this on my Xiaomi MI A3. Does it support adding a work profile/account? This is a feature that I use on my stock rom and it is essential. Thanks
Click to expand...
Click to collapse
Are you talking about the launcher (some google launchers have seperate tabs at the top to pick which profile to open an app in) or system wide (when you have a logo in the status bar/qs that you can open to sign in to another "account")?