Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "aosp"
-
Gahaa!!! Finally back home, after 7 fucking hours of sitting in busses and trains!
BUT I GOT MY NEXUS 6P!! Yoo-hoo!!! :D
And I've got a nice story about it.
So when I bought it, the guy selling it to me was a nontechnical type (I think?) whose wife was the previous owner. So I thought to myself, cool a nontechnical user used it.. probably no hardware mods or anything to worry about. Apparently they even factory reset it for me :)
Now, when I left to go back home, I of course immediately booted up the thing and did the whole doodad of logging into it, setting up the device etc.
Then it struck me. When I booted up the device and wanted to log in, there was a lock from Google that required me to first authenticate as either a previous account of the device, or their unlock pattern. So I figured, eh fuck it, I'll just flash some AOSP without GApps or send the owner an email asking what the previous pattern is.
But I still had to wait 30 minutes at the bus stop so I thought to myself.. previous owner was a nontechnical woman.. maybe I could crack it. No way to know if I don't try. So I started putting in random unlock patterns.
3 attempts later - I shit you not! - pattern accepted.
Do you want to add this account?
Oh boy Google, of course I do! Thanks for letting me in pal!
3 fucking attempts. That's all it took to crack the unlock pattern of an unknown person. 😎26 -
*decides to make a new os*
*remembers aosp*
*goes to their website*
*searches for sources*
*downloads*
*c/c++ based*
........
I ain't know a single stuff in C/C++ except that printing a string in C is printf and cout something in C++
AHHHHHHHH17 -
I've been swapping through a couple of ROM's recently for my Nexus 6P but I don't really like any of them a whole lot.. so I've been thinking to build my own from source. However I'd also like to discard Google while I'm at it, and instead go with F-droid, DuckDuckGo, and AOSP keyboard. The problem is that I currently don't see any viable alternatives to the following: Google Assistant, Google Play Services (particularly in-app purchases like those for devRant), Google Maps and Google Calendar. Which alternatives would you recommend, and which are you perhaps using yourself as alternatives? Thanks!10
-
Oh fucking Huawei.
Fuck you.
Inventory:
- Honor 6x (BLN-L22C675)
- Has EMUI4.1 Marshmallow
- Cousin brother 'A' (has bricking XP!)
- Uncle 'K'
- Has Mac with Windows VM
Goal:
- Stock as LineageOS / AOSP
Procedure (fucking seriously):
- Find XDA link to root H6X
- Go to Huawei page and fill out form
- Receive and use bootloader code
- Find latest TWRP
- Flash latest TWRP
- TWRP not working? Bootloops
- XDA search "H6X boot to recovery"
- Find and try modded TWRP
- TWRP fails, no bootloop
- Find & flash TWRP 3.1.0
- Yay! TWRP works
- Find and download LineageOS and SuperSU
- Flash via TWRP
- Yay! Success.
- Attempt boot
- Boot fails. No idea why
- Go back to TWRP
- TWRP gives shitload of errors
"cannot mount /data, storage etc."
- Feel fucked up
- Notice that userdata partition exists,
but FSTAB doesn't take
- Remembers SuperSU modded boot
image and FSTABS!
- Fuck SuperSU
- Attempt to mod boot image
- Doesn't work (modded successfully
but no change)
- Discover Huawei DLOAD
Installer for "UPDATE.APP" OTAs
Note: Each full OTA is 2+ GB zipped
- Find, download, fail on 4+ OTAs
- Discover "UPDATE.APP Extractor"
Runs on Windows
Note: UPDATE.APP custom format
Different per H6X model
- Uses 'K''s VM to test
- My H6X model does not have
a predefined format
- Process to get format requires
TWRP, which is not working
- FAIL HERE
- Discover "Firmware Finder"
Windows app to find Huawei
firmwares
- Tries 'K''s VM
- Fails with 1 OTA
- Downloads another firmware ZIP
- Unzips and tries to use OTA
- Works?!
- Boots successfully?!
- Seems to have EMUI 5.0 Nougat
- Downloads, flashes TWRP
- TWRP not working AGAIN?
- Go back to XDA page
- Find that TWRP on EMUI 5 - NO
- Find rollbacks for EMUI5 -> EMUI4
- Test, fail 2-4 times (Massive OTAs)
- DLOAD accepts this one?!!!
- I HAVE ORIG AGAIN!!!
- Re-unlock and reflash TWRP
- Realise that ROMs aren't working on
EMUI 4.1; Find TWRPs for EMUI5
- Find and fail with 2-3 OTAs
Note: Had removed old OTAs for
space on Chromebook (32GB)
- In anger, flash one with TWRP
instead of DLOAD (which checks
compatability)
- Works! Same wasn't working with
DLOAD
- Find and flash a custom TWRP
as old one still exists (not wiped in
flash)
- Try flashing LineageOS
- LineageOS stuck in boot
- Try flashing AOSP
- Same
- Try flashing Resurruction Remix
- Same
- Realise that need stock EMUI5
vendor
- Realise that the firmware I installed
wasn't for my device so not working
- FUCK NO MORE LARGE DLs
- Try another custom TWRP
- Begin getting '/cust mounting' errs
- Try reflashing EMUI5 with TWRP
- Doesn't work
- Try DLOADing EMUI5
- Like before, incompatability
- DLOAD EMUI4
- Reunlock and reflash TWRP
- WRITE THIS AS A BREAK
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH7 -
Please stop saying, "stock Android." What you mean is AOSP, and no phones from any manufacturer come with it. Stock means it's in the original state that the manufacturer intended, filled with bloat, whether it's Samsung, Google, LG, Xiaomi, or whatever.9
-
AOSP
Even though Googles decisions around it are questionable most of the time, I love that we have an (almost) completely open ecosystem for smartphones.
And the thing about it I love the most is the amazing modding community around it. -
Ouuu yesss.
I have ported init_sony and multirom.
But multirom install fucked up my init_sony kernel.
It didnt boot at all even kernel.
After discovering issue with friend we instead of fixing it( AdrianDC needs to fix that) we created a HUGE hack.
We took another library that unzips boot.img (Sony uses ELF image its different then AOSP type)
And implemented it into multirom installer.
Error.
So lets do it manually.
Success.
Shit it doesnt boot.
Ahhhhhhh.
So i added --forceelf option.
Didnt work.
So i just opened the file studied it and then HARDCODED the ELF value into type right before the image is created.
Flash it.
Real success.
Not only it worked but me and my friend created a fucking huge hack around entire multirom which is even bigger hack on its self.
I can call this productive day.
Tomorrow: Asking AdrianDC to help me on this since he edited bbootimage.2 -
Fuck you google android IME team and fuck their open source policy..
So recently i had a chance to work with AOSP LatinIME code, basically our Android keyboard was forked from very old code base of LatinIME and my job was to change its base version to latest Version available on AOSP repository. Downloaded latest Android 8 codebase. Did 2 weeks of deep investigation of what improvements we will get from upgraded code base.
And I came to know that those Google fucking cunt sucking dick heads deprecated that project and broke the whole thing to a pice of shit. Half of the code is broken with fucked up todo stuff and motherfucking missing method implementation with not implemented warnings. What those motherfucker did is that they abandoned the open-source project after they released Google GBoard, and fucked the stable code by adding quard gram support and dictionary download with multi account features which was never completed by those motherfuckers..
Those misguiding donkey shit fuckers kept a depreciated project in AOSP build tree which has not received a single fucking commit from shitty ass Google IME team, is said to be reference model of Android IME implementation..
What kind of fucking shit is going with open-source code in name of making competition high with thirt party Android keyboard developers ..
Fucking shit fucking ime team .. fuck you .. wasted my fucking time reading your shitty code base .. Fucking shit1 -
Haxk20 starts a LineageOS build without applying most of the patches he should just to build most of the shit and then add them to build the rest.
Build goes without issues to 60%.
Wooooh NO NO NO NO NO.
This is not how this is supposed to go.
You are supposed to fail at 40% then error out and make me stuck on that error for a week or so.
Short version: The port is going suprisingly well and im scared of how well it goes. Im not used to this kind of shit when stuff goes that easy. But i suppose i should thank SONY for device trees and most of the porting done. I just have to edit it a lot to make it compatible with LineageOS.
And BTW LineageOS 17 when you are done and i get working build of AOSP 10 then im coming for you. Be scared.3 -
Getting a new phone next month and its development is so far non existent on XDA.
So as you could have guessed yes im downloading sources and getting to work for AOSP build.
Oh and its SONY so its not gonna be that hard.4 -
(Dev)Life in the past 12 hours
Oh boy have the last 12 hours been a roller coaster ride for me. Noob me decided to "compile" AoSP for my device to get a taste of how custom ROMs are built from source. Overall it was fun but the errors were a very good excercise for googling, SO. Couple stuff I learnt ( possibly useful for anyone who comes here )
* The shebang line ( #!/usr/bin/env python ) on my system translated to Python 3.7 environment instead of the expected Python 2.7. Best solution I think to avoid confusion is to create a python 2.7 environment and source it.
* Get your trees right. A jar file called WfdCommon.jar ( apparently known as wifi-display common ) was the cause of several hours of hunting the fault. My vendor tree somehow didn't have this file so dex2oat was borking out like mad. I'm still amazed how I figured this one out almost by myself. ( Basically I had to check every file included in the boot class path, and find the odd one )
* I wasted a lot of time in finding the right files to change version numbers and all. Maybe I didn't search XDA properly for a guide ?
Overall it was a fun experience. Also if anyone's experienced in this area could you share resources to learn more about custom ROM development? Specifically on the tweaking part where you mix features from different ROMs to make a great ROM ( like AoSP extended or Pixel Experience ). All I could find were on the zips and not on sources.10 -
Going out on a limb here... have any of you done any bare-metal phone programming (not counting compiling like AOSP and such, like totally arbitrary code at boot-time, or bootloader coding, ideally) or know someone that has? A friend got bit by a bad iOS app on a jailbroken iPhone 8 (checkra1n, so no unsigned firms or anything) that has installed a bad iCloud lock on the device, and I need checkm8 shellcode to zero most of if not all of the NAND to get rid of it (since an iTunes restore preserves that data) and I can't figure out jack shit about how any of this works, since ARM isn't strict on what goes where in the address space or how to access hardware.15
-
I did it again.
I got myself into ROM porting again.
But i must say i have learnt a fucking lot of shit from the last time i did it.
But really i wish SONY could make the device trees more uhm custom ROM friendly because sure it works on AOSP but dang the shit that has changed on LineageOS is crazy and i have to follow all that shit to make it build even. Totally utterly crazy.
But hey at least i have all the patches that are not in the repos. That they have made easy to follow. Boy if it builds fine and after fixing the shit it boots up on first try is going to be miracle and im going to scream so hard that i will go beyond human hearing range (20Khz) Dogs will congratulate me on that LUL. -
Guess who is amazed at how fast his "I'm not gonna spend my time rooting my brand new android flagship and fiddling around with AOSP ROMs" goodwill goes in the trashcan?
.
.
.
.
.
.
Me.4 -
You know what ? I like sony xperia github and the devs. It doesnt take too long for your patch to get reviewed and they give you good feedback also.
i got new device as you may know and well adoptable storage wasnt working on AOSP. So i looked in fstab and yup it wasnt there. Added it. Posted it. Boom got merged after 7 hours.
In Ressurection Remix adding one line to manifest.xml took 2 months almost to get merged. This is ridicilous.2 -
everytime i buy a new phone ,i feel this sense of extreme regret :(
i bought a moto g 5g phone last year in feb, it was so good . it didn't had any out of the world cameras or some funky stuff, but it gave a decent performance and i couldn't want any other phone.
In October my mom's phone started giving issues so i bought a realme phone for her that was half my phone's price. i couldn't spent any mor e because otherwise she wouldn't take it. she accepted the cheaper phone and within 4 days sue was cursing it. the phone had decent specs but would lag in certain apps like zoom, and won't run some call recorder apps. at the end i swapped my phone with mom's since i didn't cared about zoom or the recorder.
now this shit realme phone's memory has gone around 60% full of my stuff, and its showing its limitations. this shit auto relaunches insta after a few minutes of usage, probably because its runtime memory gets short( 4gb 128gb device gets memory shortages. nice). its video quality is shit and camera also takes rarely good pics.
the worst thing i like about smartphones today is how they over optimise the ui. this insta issue and auto call recorders not working is simply because of the realme skin running over the stock android. i had similar issues with a xiaomi device i bought for my dad sometime ago. (fortunately my dad is more medieval so that crap has not came back to me :'/ )
so overall i am buying a 3rd phone in 17 months.
This time it's Samsung f23 and am worried that it's also going to suck. i was this 🤏close to buying a pixel 6 or even an iphone coz i can afford them.
but the regret of buying such an expensive phone that will need replacement in 2 years made me rethink.
the only android os that have suited me the best is stock and as of now only 2 companies are making it : google and moto(* it's 100% aosp with 3 extra apps but they can't say that, so they also state that they are not stock os) . one plus is also a brand that i have heard makes a good os . but recently i also heard that they have completely scrapped their os and using oppo's softwares . plus the amount of tickets we get for notifications not working in oneplus, am sure their optimization is extremely aggressive.
so everything between a moderate price phone ( that will need a replacement in 2 years ) to a flagship felt unnecessary to me, so i went ahead with a Samsung's shit phone. f23 has almost same specs as moto but it's again a heavily customised os. i wanna waste my money on trying a custom os and declare it shitty.
most of my friends that use Samsung are fan of it but they are also not very techy so i guess it suits them well. i am the guy who first installs nova launcher in his device, so let's see what it brings on the table. from the 3rd person p.o.v, i felt its screen and camera images to he nice whenever i used their mobiles, so let's see what this brings to the table :(10 -
Finally got to flash stuff onto my phone again.
Damn, Magisk is nice.
AOSP is so smooth too.
And I replaced GSF with microG. :^)7 -
OK so as expected i lasted 2 days running stock firmware on my xperia 10 Plus.
2 fucking days.
Already unlocked BT and flashed AOSP.9 -
Just got into project with 2 sony developers on making "dirty" LineageOS port over sony AOSP.
Hmmmm did i just make it boys ?
As they would say in cyberpunk 2077.
We are going to the major leagues boys. -
I have a freaking cool, useless idea, but i dunno if it will actually work
1. Put a usim in the slot
2. Reads information and connects with ISP
3. Turn on mobile data
4. Turn on hotspot
5. And useas a portable wifi
Don't ask me why you don't bring my phone, there are reasons
The os will be no screen only physical buttons with stripped down aosp
Can it work? Or in other words, is it possible?14 -
Just learn that all current and mantained sony devices that are in their open source program will get 4.14 kernel with AOSP. Very nice indeed
Also they are already working on android 10 lol.
Will report few errors i got while building and maybe it will build 😂😂😂 -
I use custom ROMs that's a known fact here. Well almost any custom ROM fails safety net. I'm taking a challenge to make safety net pass on my device running AOSP. Wish me luck.18
-
Nooooo i totally didnt unlock Bootloader, flash AOSP, Flash TWRP, install magisk on 2 days old device. What makes you think that ? Ohhh the last rant ? Well yeah.
Jokes aside. I had some real pain flashing AOSP bootimage on this phone. Fastboot for some reason didnt want to recognize that its AB device and didnt find sockets so i coudlnt flash it. After new cable the issue wasnt solved. It ended up either software shit on my laptop or just laptop usb ports. Dont know yet. Need more testing but after all this shit its all running rooted and im fucking happy.
Btw sony if some devs from your company are here. Hi and fix your shit dammit. .sin is fucking crap and devs hate it and so do i too. I never had so much issues with boot images only with that piece of shit you call .sin. fuck it. Im so glad AOSP makes normal boot.img files because if they were .sin i would jump off cliff at this point. -
postmarketOS port day uhmmmmmmmmmmmm 3.
Surprisingly to get a port of it you just need kernel which is hella awesome. What isnt awesome is the boot image of the 2012,2013 sony devices.
This is gonna get technical. If you dont care about it just skip it.
So sony decided that using ELF format for boot image is good idea. And TBH they were kinda right. ARM processor after all can execute ELF natively and work efficiently. Whats the issue then you might ask. Well kinda simple. Normal AOSP boot images are not ELF format. (They kinda are but arent at the same time. Lets just say they contain ELF image at some point). This is of course the google way. Overenginner everything you can.
So why is the ELF image format the issue ? Well to produce this elf image you need special script provided by sony that can make ELF format boot image that you have to compress properly afterwards. OK this sounds OK so whats the issue ? AOSP or well android sources do not support this out of the box. What we need to do is to create a custom way of creating that boot image. Which isnt hard but is just extra unneeded work.
Now when you flash the image it all works as expected.
But what happens if the format isnt right ?
Device will just show blank screen and reboot and so on forever (Or well until battery dies).
Why it cant boot other images is kinda self explanatory. Its different format. OK so it wont boot anything other then custom boot image OK.
Now what does postmarketOS (PMOS from now on) do ?
Well it creates basic AOSP bootimage with custom ramdisk. Which is all fine on most devices. Except here of course.
So that wont boot.
You may just say why dont you just convert it ? Well it isnt that easy. Each elf file has its own header. Which is for that kernel and etc. If it doesnt match eyyyy no boot. So we cant just convert it that easily.
Why not just use the script ? One could do that of course. ( i have not yet done that as its almost midnight and i have test tomorrow). Issue here could be that it still doesnt boot which would mean that something else is wrong. It will most likely work tho. (hopefully)
What i would need now is UART. (Yes phones have UART if you didnt know)
What is that ? Way to communicate and debug the kernel when something is wrong to the point where nothing works. Issue is my UART to USB converter is who knows where and the new one isnt going to be here that soon.
Thats all for now i guess. Long one i know. But well that is the behind the scenes of those kind of things. It isnt as simple as one may think sadly.
It woudlnt be my first and sadly not even last time i would get PM saying to hurry the development or some other shit like that. (Yes people are like that). And when you get issue it isnt as easy as opening duckduckgo and searching it as most likely it will return something which is far from what you are doing.
So if you are that kind of person that sends PMs to devs on XDA to hurry the development or asking when its gonna be done. STOP. Please just stop. We have real life too (I know its hard to believe but well its there) and doing this isnt the only thing we do. Its gonna be done when its gonna be done. And i hope this is gonna at least put some perspective for those people to not send those kinds of messages to us. (We read them. We just dont reply to shit)
TL;DR Sony decided to use different format of bootimage on 2012/3 devices which is pain to generate properly.2 -
I must say it. I love the 21:9 aspect ratio of Xperia 10 Plus. Yes sure it's little crazy but I love it already. Ohhh Reddit and YouTube is just amazing to watch.
Already have the bootloader unlock code ready.
Will probably wait until Android 10 is released for my phone tho. Or at least the sources get updated so I can build AOSP myself. Then oh boy custom ROM run will begin for me.5 -
Just got my new phone today. My old Huawei was acting up, so I replaced it with an island model: an Asus. Man, I have read lots and lots of horror stories about bloatware that came with the previous version of their skin, ZenUI. Their UX people must have been listening, because this phone came with fewer preinstalled apps than any phone I've ever had, and that includes a Nexus 5. And so far the only preinstalled apps I've had to disable are the default keyboard and chrome.
It's as close to AOSP as I've ever had without using a rom. I'm pretty stoked! -
I'm thinking of moving on from LineageOS. It's pretty good on my S3, but the battery life is laughable and there's some in built features missing I'd love to have.
Maybe make my own? I have trouble finding ROMs for my phone (that I like)7 -
The biggest dilemma for me has always been whether to switch my Android device to a sleek beautiful customisable AOSP based ROM or keep the stock ROM with all the amazing drivers and features, but with crappy bloatware.
Been sticking with CM/Lineage for years, amazing experience with Xposed & Viper4Android, but at expense of things like 4K and slow motion video and other stuff. -
I am learning C++ and I want to develop my own custom ROM for android from AOSP which is Android Open Source Project. I don't know anything about how to do it help on internet is not clear and on the Android official website there is no section for documentation and people on other sites say read documentation.5
-
Speaking about notifications, would it be a deal breaker to go back to Android 10 after experiencing notifications from Android 11 🤔rant debugging lineageos android dev aosp java development android development resurrection dev android android studio
-
some things I found in AOSP code good to see that I am the only one who writes bad patches to make things run .