####After seen lots of tutorials i know how to build rom and made one
But
There are few questions i couldn't found for google, or difficult to found------
1) how to make lineage os for unofficial device?
2) how to make update build with same rom and latest security patch?
3) how to edit buildprop and updator script once and no need to manual update in updated build?
4) how to solve bootloop related bugs ?
5) how to fix heat related and sensors related issues?
6) is there any script or kitchen which can help me to update or tweak roms from source insted manual typing commands
Thanks in advance
Related
Hey guys!
All of you know that my Nitrogen (link) uses mik's patch and does not work.
Well, aspee gave me idea and I started to work on it again (THANKS ASPEE!)
So I need some testers to test if my updated patch DOES work.
For the ones who are willing to test:
(*) MAKE SURE YOU ARE ON NEW BASEBAND
1) flash this: OLD BASEBAND NITROGEN
2) And flash this: updated patch
3) test if data works.
If it doesn't, reply in this thread or PM me. If it doesn't work, I will be editing the build.prop and adding more files.
I ABSOLUTELY DON'T THINK I just fixed this, as many dev's were on this for a really long time, but there is a small chance.
backup for later
Hi,
I know there are a lot of guides out there but you still might want to read it
What are the different things I need to know ?
Well you will hear three terms very often. Baseband, Kernel and the ROM. Lets see what they are.
Baseband :
A firmware to drive the radio (2G/3G) chipset in your phone. Most of the time you don't need to bother thinking about it. But you might need to upgrade this firmware in order to get optimum performance. Just think of it as something you won't need to apply unless explicitly specified. For you xperia neo v, you can find out the baseband version by going into phone info and looking up baseband version number. I have not flashed any baseband. I recommend if you have not rooted/flashed your phone, install the official sony update you'll get the latest baseband without any troubles, this is what I did. Although if you need to flash it, there are very many tutorials available on this forum. You can check out the flashtool androxyde . github . com / Flashtool (sorry for the spaces in the links. I can't post outside links because of some forum rules which don't make any sense whatsoever)
Kernel:
This is the Linux (android) kernel image that drives all the hardware. Always install (flash) the recommended kernel for any ROM. Installing kernel and ROM is an absolute must.
ROM:
This is the actual thing you see running on your phone. It consists of the modified android source, user interface tweaks, the apps and some under the hood modifications done by the ROM developer for ex. cyanogenmod.
Now lets setup you linux (ubuntu) install fo installing a custom ROM on your phone.
Follow this wiki : wiki. cyanogenmod. com / wiki / Howto:_Install_the_Android_SDK
Don't forget to setup Udev by making a file /etc/udev/rules.d/51-android.rules with contents as
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="plugdev"
now restart your udev daemon by running "sudo restart udev".
Now yo have the necessary kernel and ROM flashing tools at your disposal. I am going to tell you how to achieve a fast and very battery efficient cyanogenmod install.
1) Download CM9 ROM and gapps(for google apps) from here
ROM: download. cyanogenmod. com /get / jenkins/4630/cm-9.0.0-RC2-haida.zip
Gapps: cmw. 22aaf3. com/gapps /gapps-ics-20120317-signed.zip
Copy these two zips to your phone's sd card.
2) Download night elf's kernel for cyanogenmod 9 from here mediafire. com /?nm7g0zid8aazfl1
3) Follow this guide wiki. cyanogenmod. com/wiki/Sony_Ericsson_Xperia_Neo:_Full_Update_Guide
But instead of flashing the kernel inside the zip, flash the night elf's kernel (just provide the path to night elf's kernel instead of the ROM's boot.img).
4) As told in the link given in above step flash both the zips. Before flashing you may also clear the Dalvik cache by going into advanced options in the recovery menu.
5) Reboot your phone. Don't turn off the GPS !!! There is a bug in CM9 RC2 which results in substantial hit on battery life. Just let it be. Anyways the GPS antenna is turned off unless any application is using it.
I am having approx more than two days of battery life with light/moderate usage (No data connection, occasional wifi).
CM9 may not be the best looking ROM. But I can assure you nothing beats it in the performance and the default setup (its very sane !!! No need to change anything at all). Also I only trust cyanogen community with all my very personal information (its my phone, it has everything !! ). If you need eye candy more and are comfortable with taking privacy risks, you may try MIUI and the dozens more ROM in the thread. I am not trying to offend anyone, its just my opinion, feel free to call me paranoid.
Always keep in mind that there are no stupid questions only stupid answers Ask away !!
I wish you a free and serene future.
I am however more interested in using the source code provided by Sony with AOSP and compiling the system image by myself.
I know how to compile AOSP, but the files provided by Sony doesn't seem to contain the `device` directory.
Also is it possible to use the AOSP and compile a ROM that is exactly the same as the stock ROM?
I haven't done any reading or experimentation on the subject but as far as I know, Sony only provides the stock kernal sources, some hardware support libraries (not all for ex HDMI, xLOUD still not provided). You can compile the kernel from Sony sources. Android image and apps are not provided by sony. All the ROM makers who are releasing ROMs based on stock are modifying the stock ROM image to do it.
For compiling your own ROM, you will have to do it form AOSP or cyanogenmod (FXP) sources.
Hi guys, i'm new to Android development. I built Paranoid Android from source for TF101. The ROM was nice and i'm happy with my ROM. So now i'm so curious about what developers do regarding building a ROM and updating it.
1. If the ROM had bugs/problems, how can i analyze it and find the root cause of the bug?
2. How can i fix the bug? Do i need to edit a file in the ROM?
3. Every ROM that had updated build from source has an changelog, how can i know what is the changelog?
I'm sorry if the questions are quite noobish. I'm new with it. Thanks
Firstly, A very Good day to all the awesome people at XDA and my fellow SGS2 users !
To begin with, I am completely new to this scene, so please bear my lack of know-how.
I have a SGS2 GT i9100 and after years of running the stock JB 4.1.2, I have decided to install the new KitKat ROM 4.4.2. So after days of researching I am considering the use of CyanogenMod installer to install the new ROM, since it seems like a safe and stable bet and Philz-CWM as recovery ( Thanks to @Vivek_Neel 's advice ) - Is this a reliable method to move ahead with ?
Also, just to clarify the order doing things - Flash Philz-CWM ( v 6.25.0 ) >>> Then run CM Installer or is it the other way round
Before I do anything, however, I have some doubts which I am hoping to get clarified :-
1) [Regarding CyanogenMod Installer] - Off the many DIY's that I came across regarding installing the new KitKat ROM, almost everyone seems to mention downloading the Main ROM file and Google Apps file and transferring it to the phone before starting.
So If use the CM Installer, do I too need to download and transfer to my phone - the Google Apps and/or any other ancillary files ( if so, which ones ) or will the Installer do it by default ?
2) According to the CM wiki, CM Installer will install a "stable snapshot build unique to the installer. These are stable builds designed to provide all core features and functionality of the device." - What does this mean in layman English ? Also all the guides for installing the KitKat ROM are using "Nightlies" - So which one should I use - What's the difference ?! And will the CM Installer install KitKat 4.4.2 ?
3) Just to clarify, after installing the Custom ROM, will I be able to download and use apps as I was doing when I was using the stock JB 4.1.2 ?
Once again, please bear with my rookie-ness and I look forward to your answers.
Cheers !
Hello everyone,
I don't know if this is the right place to ask, please move to the appropriate section if needed.
My question - let's say I have a rom on my device that is no longer maintained by the developer, is there any way through which I can manually update Android security patches or maybe maintain the rom myself??
** considering that I don't have any custom kernel available or its no longer updated at all.
Can anyone help me with this?
good question