Related
I love CyanogenMod, I really do. It is constantly improving and the devs working on it obviously work very hard to keep things running smoothly. However, with a codebase this large, constant improvements inevitably leads to a fairly consistent stream of new bugs amidst the improvements. I understand that nightlies are not intended to be used as daily drivers, although usually they are stable enough for most here at XDA.
Acknowledging all of this: I can't help but wish on some days that I could take the excellent skills/care/devotion of the CyanogenMod team and have them devote a fraction of their work to create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs. This would be an incredible stop-gap between the initial build of a new CM nightlie (say, CM11) and the inevitable stable release.
This is NOT a statement against the added mods/apps to CyanogenMod (File Manager, Apollo, DSP Manager, etc.), I am very much of the opinion that these additions are beneficial, even necessary to the growth of CyanogenMod.
I do not expect this to happen, and I especially do not expect them to go back through CM10 and line-by-line strip all of their adjustments/additions. I understand that they are all very busy at work to keep us happy, and I appreciate that. Think of this as wishful thinking from a big fan.
Am I alone in this opinion?
it is called an AOSP rom. in this case vanilla. get a nexus device for that
Obviously, but I think you're missing my point...or you didn't read my post.
ohfoxxxycole said:
create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs.
Click to expand...
Click to collapse
A vanilla android rom with a custom kernel
Sent from my SPH-L710 using xda app-developers app
XxSilent.NightmarexX said:
A vanilla android rom with a custom kernel
Click to expand...
Click to collapse
Yes, but done by devs that know what they're doing.
Every single dev here knows what they are doing. Plus aosp is easy to compile for any device
Sent from my SPH-L710 using xda app-developers app
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
no, thats just because AOSP roms lack features that people crave from CM or AOKP
Alright, so we're back to my initial post now.
In other words an aosp pure android rom is not people look forward to. Cm10 stable rom is there and probably with like one minor bug or two.
Sent from my SPH-L710 using xda app-developers app
I know how you feel; I wish they would release a stable ROM for those that prefer stability over speed/features
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Click to expand...
Click to collapse
this is true, but i'd be using this with mostly stock software + social network feeds and games only
the milestones are a great idea, and probably the closest thing im going to get to this, but they are still snapshots of mostly stable aosp with many many tweaks to keep modifications that i may or may not use stable. not exactly ideal, but thanks for the suggestion. i'll probably stick with the newest m build when it is ready.
im not asking for cms device tree compiled as it is, or anything at all. im just hoping that before or adjacent to cm11 getting going with mods and tweaks that they will release builds tailored to vanilla and nothing else, concentrating only on bugs before adding things and testing them and adding things and breaking things and testing them and so on and so forth. i feel im not communicating this efficiently and im sorry
$MyName said:
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
Click to expand...
Click to collapse
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
hayzooos said:
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
Click to expand...
Click to collapse
I was using m2 for quite a while before I switched over to bb6. In my time playing with m2 I found that video recording was fine and data connectivity took about 10 seconds longer on a reboot. Other than that I've experienced no data drops.
To add to this, YMMV. I'm not sure if my phone is different somehow but I've never had any of these problems that people describe with data drops at random.
Edit:
Also, as far as lte/3g hand off goes, I'm unable to test as I'm not in an lte area. As for GPS, it takes about 7 seconds to lock on in a room with no windows. Tested on slimbean, so again YMMV
Sent from my SPH-L710 using Tapatalk 2
Just try looking into building aosp from source its really not that hard it will just take some time. You could even use the device tree for d2spr from cm so you really will just be using pure stock
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
Click to expand...
Click to collapse
You're clearly smoking some good crack. AOSP ROMs for the E3D are awesome right now.
Months ago
Sent from my SPH-L710 using xda app-developers app
Plain old SGH-T999 that I've flashed with CM 10.1.2, 10.1.1 and 10.1-nightlies. I format and wipe the cache/data/etc and do zip installs from the MicroSD with TRWP. I'm using GAPPS (20130301) from goo.im
Google maps crashes when you're navigating and get a call and re-enter the app without using the system bar. I've experienced quite a few other crashes that I never did on the stock TW ROM. CM takes the stance that gapps are not supported, yet what good is CM without it?
I was at a major ballbark and could barely get data-connectivity while iPhone and other S3/4 stock ROM users were loading pages at lightning fast speeds while I'm getting timeouts to google.com. That seems to have improved when reflashed nightlies and set it to GSM/WCDMA auto. (Why does the tmobile build of CyanogenMod even show the CMDA/EvDo options?)
Is Cyanogen just not any good if you want a rock solid AOSP type daily driver?
I'm not trying to rip on Cyanogen developers, I'm just frustrated I can't seem to get a stable stock android experience on the S3. All the other ROMs seem to be recompiled junk that focus on theming and and useless UI modifications or overclocking/kernelmod garbage.
First off, probably not a good idea to be bad mouthing the development on these forums which is FREE of charge to you. That gives you no right to complain about the work of the devs on this site. However, if you want a stable aosp rom, I would highly suggest liquid smooth.
If you want a stable CM rom you might want to stay away from nightlies which are experimental roms which usually contain bugs. You should be trying to flash the stable builds.
Edit: I also see that you didn't mentioning wiping the system partition when you flash roms. You're supposed to wipe system, data, cache and Dalvik cache before you flash a new rom with gapps.
gyrfalcon said:
I'm not trying to rip on Cyanogen developers, I'm just frustrated I can't seem to get a stable stock android experience on the S3. All the other ROMs seem to be recompiled junk that focus on theming and and useless UI modifications or overclocking/kernelmod garbage.
Click to expand...
Click to collapse
That's interesting, I've never seen anyone be so rude and call all other ROMs recompiled junk that focuses on theming and useless UI modifications or over clocking/kernel mod garbage. I seriously don't know how you can b*itch and whine about something you get to use free of charge. Here's an idea, don't use it.
You know what, I'd like to see you build from source and release your own ROM, let's see how that turns out.
Sent from my SGH-T999 using xda premium
Da Kine said:
You know what, I'd like to see you build from source and release your own ROM, let's see how that turns out.
Click to expand...
Click to collapse
marcoxx626 said:
First off, probably not a good idea to be bad mouthing the development on these forums which is FREE of charge to you. That gives you no right to complain about the work of the devs on this site.
Click to expand...
Click to collapse
Just because something is released for free doesn't mean people don't have a right to complain about it. Ubuntu garnered a ton of complaints when they released the unity interface, and rightfully so.
marcoxx626 said:
However, if you want a stable aosp rom, I would highly suggest liquid smooth.
Click to expand...
Click to collapse
How is liquidsmooth going to be any better than CM when it's built off the CM 10.1 code branch? Did they improve the code and somehow that didn't backflow back to CM?
gyrfalcon said:
Just because something is released for free doesn't mean people don't have a right to complain about it. Ubuntu garnered a ton of complaints when they released the unity interface, and rightfully so.
How is liquidsmooth going to be any better than CM when it's built off the CM 10.1 code branch? Did they improve the code and somehow that didn't backflow back to CM?
Click to expand...
Click to collapse
One thing is to complain, another thing is to be disrespectful. Calling CM garage, is straight up being disrespectful. Like in any environment, constructive criticism done respectively will go alot farther name calling and being overall rude.
LoopDoGG79 said:
One thing is to complain, another thing is to be disrespectful. Calling CM garage, is straight up being disrespectful. Like in any environment, constructive criticism done respectively will go alot farther name calling and being overall rude.
Click to expand...
Click to collapse
I never called CM garbage, but it's not stable from my experience with it on the S3 and other "supported devices". I did refer to " All the other ROMs" as recompiled junk though. If those developers are hurt I they can not read my posts, just like I won't use their junk.
gyrfalcon said:
Is Cyanogen just not any good if you want a rock solid AOSP type daily driver?
Click to expand...
Click to collapse
The answer is yes. I've flashed 10.1 stable and 10.1.2 and had minor bugs with the new features. By far the more stable ''bug less'' is the CM 10.0 stable build. Rocking it since 3 weeks i've even not faced a FC or a bug.
And a personnal note for you, those guys make free content for our community, they are not paid for this and this is not their job so dont be rude with them. Look at sammies release full of bloatware and FC, those guys are paid to make that.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank your for your cooperation
Friendly Neighborhood Moderator
Perhaps you should save for a Google phone and next time not purchase a TW infused phone
Thread closed
Kinda redundant since adityaxavier just put his build up, but here's what I built last night. I can't test it since I'm still not home (I built over SSH), but I think I fixed some if not all of the problems it was having. If I end up getting working builds as good as adityaxavier's, maybe I'll turn this into an unofficial nightly thread. I'm really hoping crespo4g can be included in CM's official nightlies again!
Alpha 2
This is the first build that I've gotten to boot, so I figured I'd post it here.
It's very very buggy as of yet (like FCs everywhere). I'm working on resolving the issues, but it's source built (not a port) and it boots.
So people might want to mess around with it. Obviously I take no responsibility if you brick your devices.
Download
Code:
Hey all,
This is in the works, if it ends up building and booting out of the box, we'll have working CM11 KitKat for our Nexus S 4G devices.
I'm not really a dev, mainly a hacker/tweaker/modder, but we'll see how this goes.
Here's my GitHub repo, I forked CM's 10.2 crespo4g sources and made some minor changes to update to the CM11 tree.
[url]https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0[/url]
Check back for goodies soon!
EDIT (10:51PM PST) I made a dumb, dumb, dumb mistake. I was extracting proprietary blobs from a CM10.2 build I had installed on my phone, and all the WiMAX blobs were missing from the manifest.
Just flashed back to stock and retried the process. All blobs synced without a problem. Rookie mistake. Building yet again. Hopeful this time it will work.
NOTE: This does not mean we'll have working WiMAX yet. I anticipate it'll still be broken from 10.2... sorry =[
[QUOTE]============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4
CM_VERSION=11-20131127-UNOFFICIAL-crespo4g
TARGET_PRODUCT=cm_crespo4g
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a8
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-13-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KRT16S
OUT_DIR=/home/josh/android/system/out
============================================[/QUOTE]
Dude you're so awesome, thank you so much! I thought our nexus s 4g had met its end. Can't wait until there's a preview. Keep up the good work.
jcruz767 said:
Dude you're so awesome, thank you so much! I thought our nexus s 4g had met its end. Can't wait until there's a preview. Keep up the good work.
Click to expand...
Click to collapse
I think having the blobs from 4.1 did it. Everything is zipped and ready to flash. I'm gonna test it (have to reflash CWM since I went back to stock) and if it works I'll upload it for people to test.
This is awesome to see. My wife has a NS4G that I think would have new life breathed into it with 4.4. She's on 4.2 right now and, unless it's OC'd by a good amount, it chokes on everything.
Migital Warfare said:
This is awesome to see. My wife has a NS4G that I think would have new life breathed into it with 4.4. She's on 4.2 right now and, unless it's OC'd by a good amount, it chokes on everything.
Click to expand...
Click to collapse
I don't know if I'd count on 4.4 being a lifeline to speed. 4.2 runs significantly better than 4.4 on my Nexus One.
That said, I'd limit concurrent processes in your developer settings menu regardless.
I think there's problems with yesterdays CM tree, the ROM I built had so many FCs it was unusable on the crespo4g, so I built for the mako (Nexus 4) from the exact same sources and had the same issues (which I've never had before building CM for the mako).
Trying a build from pure AOSP right now. Will keep you guys posted. PM me if you want the buggy ROM, otherwise I'll toss it.
jc4gavejc said:
I don't know if I'd count on 4.4 being a lifeline to speed. 4.2 runs significantly better than 4.4 on my Nexus One.
That said, I'd limit concurrent processes in your developer settings menu regardless.
I think there's problems with yesterdays CM tree, the ROM I built had so many FCs it was unusable on the crespo4g, so I built for the mako (Nexus 4) from the exact same sources and had the same issues (which I've never had before building CM for the mako).
Trying a build from pure AOSP right now. Will keep you guys posted. PM me if you want the buggy ROM, otherwise I'll toss it.
Click to expand...
Click to collapse
I just want to thank you for your effort regardless of how far you get! I was begining to think the cerspo4g development was dead!
I was thinking about trying to get the crespo CM11 to boot on our devices but I know NOTHING about cooking roms. I just couldn't find the time (too many other projects renovating a FG camper, minecraft server, fixing the car, work, family etc..)
Sooo... THANK YOU! :good:
i'm in to test any build for crespo4g... i won't be able to test data/cell b/c i use this device for listening to music only... would be great to have this on my NS4G though... was looking into making it myself but idk how to do it either lol
Thanks for working on this. I am only using the NS4G as a WiFi device for now, but would love to play around with anything 4.4
Sent from my LG-LS970 using Tapatalk
the1dynasty said:
i'm in to test any build for crespo4g... i won't be able to test data/cell b/c i use this device for listening to music only... would be great to have this on my NS4G though... was looking into making it myself but idk how to do it either lol
Click to expand...
Click to collapse
I'll post it here when I get a working build, right now I'm trying to merge some of cn.fyodor's optimizations from the original Nexus S build. It might end up being pure AOSP as opposed to CM, depends on what I can get to build without errors or other post-build problems. I don't have a ton of time to work on it over the next couple days, but I'll try to do what I can.
jc4gavejc said:
I'll post it here when I get a working build, right now I'm trying to merge some of cn.fyodor's optimizations from the original Nexus S build. It might end up being pure AOSP as opposed to CM, depends on what I can get to build without errors or other post-build problems. I don't have a ton of time to work on it over the next couple days, but I'll try to do what I can.
Click to expand...
Click to collapse
Thanks... Enjoy some turkey today if that's your thing... Personally, I've been using stock for a few months on my N4 and now on my N5 I only rooted to remove some apps and install a custom kernel... I prefer stock to mods now... Mainly because I don't have time to keep up with updating so often... So a stock 4.4 ROM on my NS4G will work for me... I already have the GEL and that runs great for me but I'm still missing the complete 4.4 on it that's why I wanted to flash it lol
Sent from my Nexus 5 using Tapatalk
+1 for full stock
I prefer full stock myself. Google's been giving such sweet goodness lately, it's really the best way to go. Plus if anyone wants to they can customize to their heart's content. I'm very hopefull you'll get this working fully - as stock.
There's really no such thing as stock when it comes to devices outside of Google's support line. Technically if you want stock its a 4.1.1 factory image from Google. AOSP is close to stock but doesn't include any proprietary Google apps by default. You can remove/add any packages you want via adb and create a "stock" ROM, but you can do that coming from any base be it AOSP, CM, or whatever. Personally, I prefer CyanogenMod. That's why I'm working on getting this build working.
Sent from my Nexus 4 using Tapatalk
by "stock" i mean no extra features added...
Right, same here... just not having custom anything - adding gapps is fine, but not custom kernels, themes, etc.
First build up. It's very broken. beware.
I'm just glad you're still working on it, I thought you had given up on 4.4 for the nexus s 4g
---------- Post added at 12:33 PM ---------- Previous post was at 12:00 PM ----------
jc4gavejc said:
First build up. It's very broken. beware.
Click to expand...
Click to collapse
Should we flash any of the stuff from your other 4.4 thread? CMDA fix, or Superuser?
Jfuginay said:
I'm just glad you're still working on it, I thought you had given up on 4.4 for the nexus s 4g
---------- Post added at 12:33 PM ---------- Previous post was at 12:00 PM ----------
Should we flash any of the stuff from your other 4.4 thread? CMDA fix, or Superuser?
Click to expand...
Click to collapse
Nothing except gapps. I'd be impressed if you could get very far with this build though. I made some changes to my source tree, I'll get a new build up tomorrow morning.
I'll give it a go and see what happens on mine. Just got this nexus s 4g from my sister, she had it on Sprint, while visiting her I asked if she had any old Sprint phones she's not using so I can try it out on Ting.
Got two of them now, one for me and one for wife. I have my wife on a stable 4.3 HellyRom, I don't have any problem trying out beta (alpha?) roms on mine though.
I'm going to try it with those two 4.4 tweaks (bionic and dalvik), plus I have a few radios downloaded I can try with it.
I'll let you know how it goes
Edit: So far, it's 'booting', but only to the first set up page asking me to set up a cyanogen account, where I'm constantly bombarded with FC's stating the dialer and systemui have crashed, those happen consistently for a minute or so until the phone reboots and starts the process over again.
I'm going to try flashing a version of Googlephone I saw on another thread after flashing ROM/Gapps, see if that does anything.
I've decided I like this phone enough to start trying some dev work on it. Might take me a while to get back in the loop (last thing I did dev work on was my first android phone, the HTC Hero on Sprint... Looooonngg time ago)
Gonna finish setting up a VM with Ubuntu on it tonight and toy around with some building working with what we've got so far to hep get 4.4 running on the Nexus S 4g
Jfuginay said:
I've decided I like this phone enough to start trying some dev work on it. Might take me a while to get back in the loop (last thing I did dev work on was my first android phone, the HTC Hero on Sprint... Looooonngg time ago)
Gonna finish setting up a VM with Ubuntu on it tonight and toy around with some building working with what we've got so far to hep get 4.4 running on the Nexus S 4g
Click to expand...
Click to collapse
You have my Github repo? I've merged all the necessary changes for the crespo4g in my device tree here:
https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0
I'm almost done with another build, I actually had openjdk7 installed before, so switched to oraclejdk6 (the one I should have been using).
That might just make the difference in the fcs. There's no other reason why my build shouldn't be working as perfectly as the ones they have for the crespo. Seriously, they're the same device minus the radios.
Hope stuff goes well for you, it'd be fantastic to have another dev working on this.
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.
postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.
Hey,
I have a Poco F3, I unlocked the bootloader recently, and I want to know which ROM should I get or is the best for you. I tried xiaomi.eu, but I prefer AOSP/pixel (I tried some, but I can't make a choice). What is the best, I know for now there is crDroid, Pixel Experience Plus but unofficial, Pixel Extended, etc Should I wait for more stable, official or new custom ROMS ?
What are the pro/cons or features of each ?
|
|
Edit : anyone can share his opinion here and/or ask on this thread
|
|
Thanks in advance !
In terms of features you can't get more feature rich then crdroid. Most ROMs are rock stable and the one main missing feature dt2w is going to be coming in the next week or so. I'm currently using pixel extended and I've had no problem and am thoroughly enjoying it
Robert314 said:
In terms of features you can't get more feature rich then crdroid. Most ROMs are rock stable and the one main missing feature dt2w is going to be coming in the next week or so. I'm currently using pixel extended and I've had no problem and am thoroughly enjoying it
Click to expand...
Click to collapse
Thank you, I'm currently using crDroid but the lack of Google Apps bothers me. I was using pixel extended but I had some bugs. I might retry, I'm hesitant for now with pixel experience plus too.
NonoBow85 said:
Hey,
I have a Poco F3, I unlocked the bootloader recently, and I want to know which ROM should I get or is the best for you. I tried xiaomi.eu, but I prefer AOSP/pixel (I tried some but I can't make a choice). What is the best, I know for now there is crDroid, Pixel Experience Plus but unofficial, Pixel Extended, etc Should I wait for more stable, official or new custom ROMS ?
What are the pro/cons or features of each ?
Thanks in advance !
Click to expand...
Click to collapse
hentai is best
No_Name188 said:
hentai is best
Click to expand...
Click to collapse
Does DT2W work on hentai? {Mod edit: DIscussion of or support for that respective OS is not accepted on XDA}
shapeshift and havoc has working dt2w. upcoming roms should have em too. most roms are under testing atm
NonoBow85 said:
Thank you, I'm currently using crDroid but the lack of Google Apps bothers me. I was using pixel extended but I had some bugs. I might retry, I'm hesitant for now with pixel experience plus too.
Click to expand...
Click to collapse
How can a rom lack Google Apps as you can install them through the playstore ?
ps : it nice not to rely to much on Google btw
Thanks for all the response, I am waiting for more stable releases, but for now I'm with pixel extended still with some bugs, but the best that I've tested so far.
NonoBow85 said:
Thanks for all the response, I am waiting for more stable releases, but for now I'm with pixel extended still with some bugs, but the best that I've tested so far.
Click to expand...
Click to collapse
hentai without bugs, with its own core where cool autonomy and adaptive screen frequency
No_Name188 said:
hentai without bugs, with its own core where cool autonomy and adaptive screen frequency
Click to expand...
Click to collapse
I might try it, but is there cool features ?
NonoBow85 said:
I might try it, but is there cool features ?
Click to expand...
Click to collapse
No, it's full clean rom with gapps
No_Name188 said:
No, it's full clean rom with gapps
Click to expand...
Click to collapse
OK, thanks !
Running Lineage on mine, with Quantic kernel, Micro-g, I am getting insane battery life, This phone has been an amazing upgrade for me after being on Mi6 for over 3 years.
for a beta Build, I have yet to run into a single issue, everything is running smoothly.
I have the feeling this phone will receive lots of love from developers and will have custom roms for years to come.
Edit: on my build I have finally fixed battery drain when, double tap, ambient pick-up, or AOD is enabled, it makes no difference, my phone dozes beautifully at night. How is it with other ROMs?
The key for me and everyone i think is the kernel, no matter what I changed with the original kernel that comes with lineage the phone gets no doze, only when I use Quantic + Lineage everything is 100%.
Barracuda77777 said:
Running Lineage on mine, with Quantic kernel, Micro-g, I am getting insane battery life, This phone has been an amazing upgrade for me after being on Mi6 for over 3 years.
for a beta Build, I have yet to run into a single issue, everything is running smoothly.
I have the feeling this phone will receive lots of love from developers and will have custom roms for years to come.
Edit: on my build I have finally fixed battery drain when, double tap, ambient pick-up, or AOD is enabled, it makes no difference, my phone dozes beautifully at night. How is it with other ROMs?
The key for me and everyone i think is the kernel, no matter what I changed with the original kernel that comes with lineage the phone gets no doze, only when I use Quantic + Lineage everything is 100%.
Click to expand...
Click to collapse
Did you flash the kernel only via TWRP or is it TWRP and fastboot dtbo?
Also, have you had issues surrounding running apps like Google Maps or Kodi? They install and boot up but crash seconds later.
best currently MIUI BASED rom? ive tried miui.eu but ive found some bugs.
Barracuda77777 said:
Running Lineage on mine, with Quantic kernel, Micro-g, I am getting insane battery life, This phone has been an amazing upgrade for me after being on Mi6 for over 3 years.
for a beta Build, I have yet to run into a single issue, everything is running smoothly.
I have the feeling this phone will receive lots of love from developers and will have custom roms for years to come.
Edit: on my build I have finally fixed battery drain when, double tap, ambient pick-up, or AOD is enabled, it makes no difference, my phone dozes beautifully at night. How is it with other ROMs?
The key for me and everyone i think is the kernel, no matter what I changed with the original kernel that comes with lineage the phone gets no doze, only when I use Quantic + Lineage everything is 100%.
Click to expand...
Click to collapse
Hi! Is there a thread or telegram for Lineage build for Alioth? Thanks!
myogui said:
Hi! Is there a thread or telegram for Lineage build for Alioth? Thanks!
Click to expand...
Click to collapse
I believe there is a telegram group, I don't have telegram or any other chat app so I rely on XDA. I am using my own Frankenstein build though, where I borrowed features from all roms but I use lineage as base.
Barracuda77777 said:
I believe there is a telegram group, I don't have telegram or any other chat app so I rely on XDA. I am using my own Frankenstein build though, where I borrowed features from all roms but I use lineage as base.
Click to expand...
Click to collapse
What tools do you use to make rom?
Hackmau5 said:
What tools do you use to make rom?
Click to expand...
Click to collapse
Source code and a Linux PC. Many tutorials on the net.
Barracuda77777 said:
I believe there is a telegram group, I don't have telegram or any other chat app so I rely on XDA. I am using my own Frankenstein build though, where I borrowed features from all roms but I use lineage as base.
Click to expand...
Click to collapse
Nice! If you are comfortable sharing a build I would surely try it once I receive my device, I've been on Lineage for years!