Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !
Related
Just read the news about these two getting the update that fixes the SMS bug but no mention of any other 2.2.x O/S'd phones getting it. Can't be far off surely?
http://phandroid.com/
I just want that SMS fix, I've seen two I9000Ms do it. I pinged Samsung Canada on Twitter, we'll see what their response is.
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
Click to expand...
Click to collapse
maybe ayes maybe naws
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
(American variant releases not guaranteed)
Click to expand...
Click to collapse
Fixed that for you.
i somewhere read that we can expect 2.3 for SGS for the end for the first quarter of the year...but are you people using stock ROMS ? i think Darky's ROM is working on a multi-device able to detect and flash devices accordingly, shouldn't that fix your sms problems ?
ps: i have the i9000, but what is "the sms problem", i don't think i have it..
Everybody bug samsung to skip 2.3 and prep for 3.0.
With carriers charging 15-20¢/SMS and having a free replacement (google voice, google talk, emails)
I really couldn't care less about SMS. I should even remove the SMS app from my phone.
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
It's for both.
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
So wrong, it hurts.
rumor
the rumor is here :
i like the way they say
"site called SamFirmwares – one we’ve never heard of before."
Click to expand...
Click to collapse
they better all listen to these site ! i wonder how these big companies would react to
all the amazing roms out there !
JCopernicus said:
So wrong, it hurts.
Click to expand...
Click to collapse
Is it? Then prove me wrong...
From google:
Honeycomb is the next version of the Android platform, designed from the ground up for devices with larger screen sizes, particularly tablets.
Click to expand...
Click to collapse
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
t1mman said:
Is it? Then prove me wrong...
From google:
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
Click to expand...
Click to collapse
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
JCopernicus said:
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
Click to expand...
Click to collapse
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
t1mman said:
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
Click to expand...
Click to collapse
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
JCopernicus said:
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
Click to expand...
Click to collapse
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
t1mman said:
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
Click to expand...
Click to collapse
The large screen views (which never existed) are built from the "ground up" because, guess what? They never existed in the first place.
The reason it's taking 3.0 is because it's a huge jump in feature set, and qualifies as a version realease and not just a point release.
If a device has a certain feature it can access certain API from the android OS. If a device doesn't, then it can't. It's that simple.
"tablets" have the big screen feature and they can access the nested view API's. You don't know how android works. there is ONE line, which sits at 2.3.2, and it's device independent.
Just like the Nexus S can access the NFC api's because it has an NFC chip.
AOSP is the code that google/samsung/moto/acer/etc pull from, and build more on top.
Cyanogen roms are on par and equivalent(better actually) as google's roms, you can't get more "official" than AOSP. MFG roms are actually less true to AOSP as they are modified. You probably won't see 3.0 on the current galaxy line at all, but that has nothing to do whether it works on there or not.
Chill out dude! Take a deep breath....
This is getting nowhere, running in circle...
I'm pretty sure we won't see Honeycomb as a release by the makers (Samsungs, Motorola, LG, HTC, name em) on any smartphone. Don't know why this is such a big deal for you and what you don't get on the whole deal but if you want,
You can bookmark this thread and if you see an official honecomb as an official release by samsung or LG or HTC or google on a Smartphone, revive it from the archives and rub it on my face, I'll gladly take the fall...
Chill out? I think I'm just typing normally on a keyboard? Maybe I'm smashing keys, and don't recognize it?
You don't understand how android works if you think it won't appear on phones, we're not going around in circles. You're just wrong.
Hello,
I joined the xda community about a year ago, first with my Htc Magic, then with my HD2. I have the opportunity to get a Samsung Galaxy Tab from some carrier for little extra money of my current Internet plan. And for 10 €/month more, I could get the new 10.1 version...
Although I do know that logically I should choose the 10.1, I still consider the 7'. Why ? Well, it would be cheaper at first. Then, I like the 7' size more and I'm not sure I would need Dual-Core processor for Internet surfing ! Also, the 10' model's phone app is blocked by the carrier, while it's not for the 7'...
But I digress !
Before to sign up to the plan, I'd like to take the pulse of the community. It's something I always do prior to purchasing a new device. I'm use to the HD2 orgy of Roms and OS and I must say that the less-furnished Development section for the Tab leaves me thinking. I don't doubt of the quaility of the ROMS but I wonder if devs are not already leaving the Tab's development for more recent Tablets and devices.
So...If you are a serial flasher like me, is the Tab a good invesmet ? I'd love to flash later CyanogenMod releases when there will be actual Tablet versions of it (for the moment, CM7 on a tablet is still in its early months) and of course Honeycomb or even better, Ice Cream Sandwhich. Will there be dev's at that moment ? Of course, I know it's not an easy question to answer but it's more about the community strengh until today actually...
Thanks and see you soon hopefully !
cm7 + tablet tweaks = win.
with roms, ill take quality over quantity, even tho there are only 3 2.3 roms, they are all badass.
the tab7 has been the best tech device ive ever owned, i have an ipad but it lives in the draw, its just way to big todo anything with other than using it in bed or on the toilet.
I suggest get the 7inch or wait for the new 7inch (who knows when that will come)
the only negative i have is that theres so many new devices out with dual core ect... but so far it hasnt stopped me from doing anything that these newer devices can do (you can play tegra games via chainfire) but eventually it will become an issue i guess.
The carrier matters.
More dev work is being done for the GSM variants at the moment. But spacemoose1 does have an alpha hc rom and dev continues in that.
Thank you for your anwser and I do agree about quality over quantity...
I'm aware of tablet tweaks from CM7, I already used them on my 4'3 HD2 screen but that not much in comparison of the many tweaks TouchWiz seems to bring to the Android 2.2 UI. Of course, overlay means slower device but oh well...
Is it possible to easily save/back up the stock Android Rom it will be shipped with in order to restore if I need to return it under warranty ?
Thanks !
DannyBiker said:
Thank you for your anwser and I do agree about quality over quantity...
I'm aware of tablet tweaks from CM7, I already used them on my 4'3 HD2 screen but that not much in comparison of the many tweaks TouchWiz seems to bring to the Android 2.2 UI. Of course, overlay means slower device but oh well...
Is it possible to easily save/back up the stock Android Rom it will be shipped with in order to restore if I need to return it under warranty ?
Thanks !
Click to expand...
Click to collapse
Yeh, you can do a nandroid backup, or just find your stock firmware, from the website sam-firmware (i think thats it) or just brick it
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
r00tb33r said:
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
Click to expand...
Click to collapse
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
russian392 said:
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
Click to expand...
Click to collapse
Since I have no experience porting Android I can't say that you are incorrect, but isn't the binary architecture of applications the same (ARMv7-A Krait instruction set?), the screen is reasonably similar (1280x720 vs 1280x768, or Nexus 4 having 48 extra pixels on the width in portrait mode). Basically, it's not possible to just stick our device-specific kernel (and kernel modules, aka drivers) in there and have everything else just work? Before Android, I had no problems compiling a new Linux kernel for my distro with new options and applications worked just fine.
By the way, HTC promised a 4.4 KitKat update for HTC One Mini which AFAIK is 95% same as our First. Would it be possible to port that ROM? I'd still prefer Nexus though.
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
Why would there be bluetooth/camera/wifi issues? We would use our own kernel with correctly configured modules. Both First and One Mini kernel source is out, can't we just run a comparison to see what's different? From the look of it they use the same Linux kernel release, so differences should be few (at least no false positives from different module versions). If newer Android builds will use newer Linux kernel, we can add those differences that we will know of after we do the First vs One Mini source comparison.
I think running the patch program would be an easy way to find the affected source files, as files with no differences will generate no patch lines.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
russian392 said:
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
r00tb33r said:
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
Click to expand...
Click to collapse
well.
1. ive seen people try, its not as easy as it seems.
2. think of it as windows. you install it on your pc, it will take another several hours just to download and install various drivers and software for your hardware.
the thing is not just in the android OS. the os should be able to auto adapt itself to any android capable device. BUT we have to consider 1. drivers for the adreno 305 and the snapdragon 400. we also need kernel/baseband capability. the nexus is pretty much a BLANK device with absolutely nothing on it, and they install a stock kernel and stock rom. we would have to go in and make the kernel work, which hopefuly we can just use a ready built one, and then tweak the rom + kernel to fit the harware, whcih will include the capatative side of the screen, and camera, and everything else, and the ram. and that. although technicaly some of it will be there, its not as easy as you might think.
edit
see, ive worked on an ARMv6 device, and its like much harder than an ARMv7 which has alot of similarities. and mind you, im not saying its IMPOSSIBLE, and im not saying its extremely hard. im sure it can be done, but porting cm form a mimic device like the One Mini would be easier than a Nexus 4, or a Nexus 5 at that.
here. maybe this will make my point clear...its not easy eve for big companies, not just for a single person
http://www.androidcentral.com/why-you-ll-never-have-latest-version-android
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
abrahammmmmmm_ said:
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
Click to expand...
Click to collapse
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
I see what you mean, but I wasn't really aware of the great difference of the adreno 225 & 305. When checking it out I only heard there was some very minor tweaks done to the 225 to get the 305. And I'd actually give it a go if it wasn't for how easily this phone bricks, I guess I'll just have to be patient and wait to see what our great devs we've got can whip up for now
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
r00tb33r said:
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
Click to expand...
Click to collapse
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
russian392 said:
1. SWAPPING IMEI IS ILLEGAL.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2216371
russian392 said:
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
Click to expand...
Click to collapse
1. Depends, still, don't do it. I don't tell others to do it, and won't say how even if asked. But that's a feature I need hence why I choose HTC.
2. More than I need.
3. When I get around it. Fortunately it's possible to unbrick these if something goes terribly wrong (I have the JTAG pinout for this device). I am waiting on a new JTAG box from the team before I release the pinout to public... Unless of course anyone wants to donate a new box or badass logic probe or a very high speed digital oscilloscope.
4. Of course the One mini port will happen before any others because it will take the least time, however not all of us want to use it.
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.
Hi
Im new here
What is the best custom ROMs for Google Pixel 5a?
ty
ALWA7SH6 said:
Hi
Im new here
What is the best custom ROMs for Google Pixel 5a?
ty
Click to expand...
Click to collapse
Right now you have pixel experience and lineage os 18. So nothing special, this phones availability (usa and japan) will hinder it's rom development. If we are lucky, maybe we will get up to 5 custom roms.
ALWA7SH6 said:
Hi
Im new here
What is the best custom ROMs for Google Pixel 5a?
Click to expand...
Click to collapse
i have only found 4 custom roms for the phone. all AOSP roms just different variations
1. pixel experience (best. not as updated as lineageOS.)
1a. lineageOS (best. updated regularly)
2. Calxyos (big on security and removing google tracking. microg and other non tracking security apps installed. updated regularly)
3. GrapheneOS (not the best due to having to install microg and the rest of the mircog stuff to get playstore games and apps to work)
really its a toss up between experience and lineage. unless you want to go stealth. then it would be calxyos.
with aosp being the only choice base rom for the phone its extremely limited. unless a recognized developer gets his hand on one and ports over a different rom. your stuck with aosp variations
rchris494 said:
i have only found 4 custom roms for the phone. all AOSP roms just different variations
1. pixel experience (best. not as updated as lineageOS.)
1a. lineageOS (best. updated regularly)
2. Calxyos (big on security and removing google tracking. microg and other non tracking security apps installed. updated regularly)
3. GrapheneOS (not the best due to having to install microg and the rest of the mircog stuff to get playstore games and apps to work)
really its a toss up between experience and lineage. unless you want to go stealth. then it would be calxyos.
with aosp being the only choice base rom for the phone its extremely limited. unless a recognized developer gets his hand on one and ports over a different rom. your stuck with aosp variations
Click to expand...
Click to collapse
I expect it is a stupid phone and it is not supported and I regret that I bought it
TY
ALWA7SH6 said:
I expect it is a stupid phone and it is not supported and I regret that I bought it
TY
Click to expand...
Click to collapse
You don't buy google pixel for custom roms. There are other phones if you want custom roms and community support.
ALWA7SH6 said:
I expect it is a stupid phone and it is not supported and I regret that I bought it
TY
Click to expand...
Click to collapse
same here. i came from HTC, but ATT pushed my phone off their network with a load of crap how it didnt support 4g or LTE phone calls. when it actually did. they just wouldn't whitelist the phone so you could use that feature or wifi calling. so in a scramble to find a new phone i landed with this pixel. biggest POS i ever owned. i thought samsung was garbage until i got this one. its slower than my HTC U11. screen is smaller. it's sad when a 5 year older phone is better than something released in 2021. i have had nothing but problems with it since day 1. text messaging keyboard disappears. text messages disappear. text phones and link disappear. i have to open and close the app 3 or so times to get the message to pop up. maps is a train wreck. half the time i can't close the app or it goes into split screen mode and then you can't do anything. you have to reboot the phone to use it again. updating any of their apps the phone gets worse. every factory rom update is worse than the last one. they never update the base apps with each rom update so im stuck with the same broken crap android 11,12,12L all the same problems. now i know why HTC sold off their crap phones division to Google and kept the flagship phones under their wing, because they found a sucker to buy their garbage low end phone. so google could launch their rebranded HTC phones as garbage pixels.
team twrp would have to get their hands on one of these phones so they could make a proper device tree for it even then i noticed their is some key parts to the factory rom that seem to be missing or embedded into other parts of the images so porting a rom would not be an easy task. then to port a rom you would have to find another phone with similar specs as this one to make it even possible. so you are more or less stuck with Googles source codes for rom building. so then your are basically just building another AOSP rom variation.
all version i listed pull from the same source code when i go to manually build their roms. so really the are all the same rom with just their add-ons and removals of stuff with a few teaks here and there.
so for now our only hope is that on black friday they are selling this phone for $100 and some developers decide to pick one up and start some development on this phone outside AOSP builds.
rchris494 said:
same here. i came from HTC, but ATT pushed my phone off their network with a load of crap how it didnt support 4g or LTE phone calls. when it actually did. they just wouldn't whitelist the phone so you could use that feature or wifi calling. so in a scramble to find a new phone i landed with this pixel. biggest POS i ever owned. i thought samsung was garbage until i got this one. its slower than my HTC U11. screen is smaller. it's sad when a 5 year older phone is better than something released in 2021. i have had nothing but problems with it since day 1. text messaging keyboard disappears. text messages disappear. text phones and link disappear. i have to open and close the app 3 or so times to get the message to pop up. maps is a train wreck. half the time i can't close the app or it goes into split screen mode and then you can't do anything. you have to reboot the phone to use it again. updating any of their apps the phone gets worse. every factory rom update is worse than the last one. they never update the base apps with each rom update so im stuck with the same broken crap android 11,12,12L all the same problems. now i know why HTC sold off their crap phones division to Google and kept the flagship phones under their wing, because they found a sucker to buy their garbage low end phone. so google could launch their rebranded HTC phones as garbage pixels.
team twrp would have to get their hands on one of these phones so they could make a proper device tree for it even then i noticed their is some key parts to the factory rom that seem to be missing or embedded into other parts of the images so porting a rom would not be an easy task. then to port a rom you would have to find another phone with similar specs as this one to make it even possible. so you are more or less stuck with Googles source codes for rom building. so then your are basically just building another AOSP rom variation.
all version i listed pull from the same source code when i go to manually build their roms. so really the are all the same rom with just their add-ons and removals of stuff with a few teaks here and there.
so for now our only hope is that on black friday they are selling this phone for $100 and some developers decide to pick one up and start some development on this phone outside AOSP builds.
Click to expand...
Click to collapse
Problem is that this phone is sold only in USA and Japan and I doubt that community regarding rom development is high in those countries. So only enthusiasts who import 5a from one of those two countries can maybe work on it.
Also, this phone is carbon copy of 4 5g (plus bigger battery and IP ratting) even though looking at how they were build they are not the same, but main components and sensors are. So maybe porting 4a 5g ROM will be better than to build from scratch.
predragiPredrag said:
Problem is that this phone is sold only in USA and Japan and I doubt that community regarding rom development is high in those countries. So only enthusiasts who import 5a from one of those two countries can maybe work on it.
Also, this phone is carbon copy of 4 5g (plus bigger battery and IP ratting) even though looking at how they were build they are not the same, but main components and sensors are. So maybe porting 4a 5g ROM will be better than to build from scratch.
Click to expand...
Click to collapse
I come from Samsung S10e.
A company like (SAMSUNG) that has spent more than 13 years in the field of screens and phones cannot be compared with a company (GOOGLE) that has spent only 4 or 5 years.
I chose this device only for its size, battery and water resistance, but I did not expect that the Android system in it is so bad and not optional
How can build a Rom?
ALWA7SH6 said:
How i can build a Rom?
Click to expand...
Click to collapse
it is not so simple, you have to google it, learn to code and debug and it will take you some time even if you have existing ROM to copy things from.
predragiPredrag said:
it is not so simple, you have to google it, learn to code and debug and it will take you some time even if you have existing ROM to copy things from.
Click to expand...
Click to collapse
I dont have time so NO TY
ALWA7SH6 said:
How can build a Rom?
Click to expand...
Click to collapse
it's more of a pain in the ass than it's worth. on my dual cpu 16 core system it takes 2 hrs just to build it. i usually just follow the steps on the pixel experience wiki page. if you want to mod it even more you would have to learn to program in c and c++. then with everything being open source borrow someone else's mod to include into your rom. then spend hours or even days troubleshooting, debugging or fixing code. if things are not compatible.
i wish i could get a stripped to nothing rom that only makes phone calls. that's it. the rest of the garbage you can download as an app or get a magisk module to do the rest.i don't need googles BLOATWARE garbage along with all of the garbage they cram down my phone's throat to slow it down to snail pace then go oh your phone is outdated that is why it's slow. so buy this other $1000 phone and that will fix your problem. i go yeah right. the thing is a year old. how in the hell is it out dated. my piece of sh*t 10 year old laptop works just fine. once i got off bloatware winblows 10 and install winblow 10 ltsc without the extra garbage no one ever uses.
[ROM][13][barbet] PixelExperience [AOSP][OFFICIAL]&[UNOFFICIAL]
PixelExperience for Pixel 5a Barbet What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible stability...
forum.xda-developers.com