Hello. I searched the forum but didn't really find an answer.
I was until 5 minutes ago with the MIUI rom. I know the last kernel I flashed was the cyanogenmod kernel (which I used with another rom...can't remember which one because I flashed 5 roms in 1 day).
I wanted today to abandon MIUI because I was having problems with the display timeout...and some other things, compatibility with applications and details were not really good for me.
So I flashed now the rcmixhd, downloaded from rom manager. What kernel should I use?
And....is a kernel independent from the rom? Will a rom not work with the proper kernel?
*deep breath*
By going through the kernel threads, reading about them, seeing what others say then choosing a few to try, add them, try them, make a decision, keep one.
Just like your radio question and your ROM question it comes down to two things:
1. Your particular hardware capabilities - Some devices like some kernels better than others.
2. What YOU want from the kernel and how much YOU think it's the best one for YOUR situation / wants / needs etc.
Only YOU can decide what one YOU like the most subject to them working ok with your particular handset (this is particularly true for overclocking).
As a rule of thumb, if you're not fussed about over-clocking or BFS vs CFS etc. then what ever kernel the ROM creator advises.
Now please, pretty please, use the link in my sig to find more in depth answers as this question has been asked too many times already.
You don't pick the kernel, the kernel picks you.
HI all , i lunched this thread after weeks of googling and usless search for a new stock or custom rom to update my phone (samsung sgh-i857 doubletime) it's a dual screen phone with querty built-in keyboard it's from at&t and it is stuck on android 2.2.2, i'm very sad that they and after years from lunching it didn't back it up with a single soft update -_- ... and i know that there are users who bought this phone like me and seek help.. i know that it's not this easy but if you are a devloper help us by creating a custom rom for it ....if you are a user of this phone please support this thread by commenting so we can get an update for it :good: ps: i attached informations for it's cpu
Hello good sir, I like you am a noobish Doubletime user who is struggling to update it to Gingerbread. So far I have been somewhat able to use the Cyanogenmod source code and I have built a CWM Recovery for the device but that seems to have hard bricked it... I ordered a new one off ebay for $15 and I'm ready to start cooking. You have my support!
Just an update.
I have a plan I have on how to get this runnin.
1. Port CWM to the DoubleTime through Cyanogemod 6.
2. Get a working version of Cyanogenmod 6 working on the DoubleTime to hopefully free up some space.
3. Find if Gingerbread can run on Froyos kernel.
From there I'll either be building a GingerBread compatable kernel or Cyanogenmod 7 depending on compatability. Any advice or help would be very appreciated.
Being new to ROM building I'm a little lost and hesitant on flashing things but here's what I know so far.
The DoubleTime uses a Qualcomm MSM7230 same as the HTC Vision. I forked it's Github respiratory and I'll be using it as a base as recommended by the Cyanogenmod porting guide.
The partitions sizes (as a accurately as I can estimate them) are:
/cache=21.05MB
/data=176.65MB
/system=194.38MB
I may need to know the recovery partition size but I'm not sure how to find that out.
I have the recovery.img and the boot.img as well as the zImage. So as soon as the repo sync is done I'll be on my way.
I'm back again today with somewhat mixed news, I can find most of the partitions and their names (I've learned a lot today) but I can not seem to find the boot, recovery or ramdisk partitions. I'm already boggled by the what seems to be unconventional naming setup for partitions. Put all of my "notes" in a text docement in the attachments section. Any help with this is very appertiated. I can type and post anything into the ADB shell you need me too.
I'm beginning to feel like I'm talking to myself, I probably am...
Upon reading forum rules and such it has come to my attension that this is the wrong forum for this kind of thread, So I have made a new thread in the Miscellaneous Android Developement Forum that will hopefully be more useful at getting more proffesional and opinionated help.
http://forum.xda-developers.com/showthread.php?t=2651728
Hi fellow G2 users!
Got my G2 a few days ago (I know I'm about a year late) but this phone seems awesome. Model is D802.
I did a lot of reading before doing anything and so far - I am on stock LG rom, rooted, installed TWRP with autorec, flashed a volume mod and installed xposed with g2 tweaksbox. So far I have nothing to complain about.
Anyway, now come the questions - my previous phone was a sensation, and to have that fully ready to flash, it required unlocking the bootloader, S-OFF, radio flashing and root.
1. Is there anything else I need to do here? This is my main question. I did a lot of reading before posting this or doing anything to my phone. I only do something once Im completely sure I know how.
2. I've read about flashing modems of some sort and came across this link - xda wont let me post links for the 1st 10 posts... Its a site like codefi.re/autoprime
Can someone please tell me what the 4 different versions of the D802 files are?
3. Any recommended ROMS/kernels that are absolutely brilliant? I know that all devs make great roms but with specifically battery life, STABILITY, and all the LG features (like knock on and the new message reply box thing and quickmemo, etc) I have heard a lot about Pardus. Might try that out soon if I dont get any other recommendations.
4. I read about Jishnu's camera mod. The links have been deleted from his thread. Is it okay to ask if anyone has a backup? I would like to try it if possible.
5. I read about Viper Sound Mod. Is there an updated method of installing this on stock rom? The thread I found seemed outdated and half the links were invalid
Nobody?
Depends on what you want. Have you researched aosp roms? All the things you looked up are fine. Tweaks for a ton will help enrich its use but to change to a complete different operating system is what you should try out if you want to see something different. Modems usually come with the rom. Make sure you flash the correct variant for your device.
I tired from flashing the roms every days cannot find stable rom to stay with
can you share with me everyone here which rom you use now and happy with
Firstly, flashing a rom everyday isn't going to help with stability issues, and sometimes you will have scripts left over from previous rom that messes with new rom. You need sometimes 3-4 battery cycles to see if phone is stable.
We don't know what you're using your phone for... but generally it depends if you want stock rom experience or AOSP/CM.
Generally speaking, sticking closer to stock will be more stable because less modifications done. But current Lollipop isn't the best most stable android either.
With that in mind, go to http://forum.xda-developers.com/galaxy-note-3/development and find some stock (TW based) roms to try out. Make sure you do full wipes to clean previous rom (include wiping system).
*PS - it's not a good idea to ask people what's the best rom (and actually against forum rules). It's too subjective. Same with stability. How I use my phone and how others use it will also determine how stable the phone reacts, etc.
Good luck!
Best rom threads are frowned uppon and are usualy closed within hours.
But as said before try a rom for more than a day.
And make sure you wipe caches and such (also mentioned in almost every howto)
Try factory reset, and make sure you have the correct software for your hardware. As there are like 8 different types of Note3's...
And as in the nice post above this one Lollipop isnt all that stable.
Just get the rom that has what you want and test it for a week or so. and then for stability issues go to the forum thread you got it from and read up. As it might have a solution for your issues.
I would add to the above only this - Read the thread BEFORE you flash and make sure you understand the steps to follow AND what the issues are. Nothing worse than someone posting on page 10 of a thread that they have 'X' problem when it was dealt with on page 2.
Read many times, flash once is the best policy
Hello! This will be a quick post about how it was good earlier and how it can be better today, so please, stay with me.
I've been using Sony's for a while now, starting with small and cute Sony Ericsson k510i, then k550i, then wt19i (LWW), and then Xperia SP. My "flashing career" started after I've lost warranty on my k510. At that time there wasn't a lot you can do to your phone - there were several official firmwares, various customization options, and a lot of custom patches. No competition, one latest official firmware, a big library of patches that you could port to your device, if someone didn't do it already. The only competing area were a lot of graphical patches, but you could compile them together on your phone. Like today, if you were doing something wrong with your phone - you'll get a brick and it's your fault. But for every device there was an instruction, a beautifully crafted instruction on what to do and how to do everything, step by step. Almost every thread included a complete set of links to get you started. If you needed to flash a customisation after installing something, there would be a link on how to flash custom right there.
Today I have my XSP and try to do something to it. So I open one link (non-sticky, needed to bookmark it), see a lot of ROMs, part of which are no longer maintained. Finally open one of them based on performance rating, and see that it needs some kernel. So I go to kernel list, and see that it can't be flashed without recovery. What recovery? One specific recovery, because another one can't flash it. Now how do I flash recovery in the first place? I need a manual for that. Now I go to kernel and ROM page and see that no manual is available for them, too. So I open main device page and don't see any manual, so I open a sticky thread. And guess what? I don't see manual there. And that's when I start a new thread, type my problem in, and see a non-sticky thread with last post made 2nd of May 2015, and no pages link to that thread at all.
Is that how it goes this days? A newbie comes in, spends whole evening, opens 10 tabs, and still can't find anything relevant? I think we need to do something with this, revisit old threads, compile a new one-for-all guide, or at least a list of guides. And stick it, so people can actually see it. Otherwise there will be small closed community of those who already can develop and flash, and all the others who either got brick or is afraid to get a brick. Thanks.
---
UPD: And then I see that the kernel which I almost decided to flash is closed and all developers migrated to another one. I'm talking about tangerine and helium. Again, no info in the first post. And main developer openly says to users of his work - if it didn't work for you, don't use it. What's wrong with you people...
I'm deeply sorry if I offended somebody with my previous post. I'm happy that you guys do such amazing things with this 3 year phone. But damn, FULL INSTALLATION took about 10 minutes, counting PC reboot into linuxes to get fastboot working. In case someone struggles like me, use CyanogenMod instruction to get to Cyanogen Recovery; download TWRP Recovery, ROM of choice and GApps of choice; place all three ZIPs onto your sdcard; go to recovery, flash TWRP, reboot into TWRP (by pressing volume rockers while loading), do Wipe - Factory Wipe, flash ROM, flash GApps, reboot to normal. Wait for about 5 minutes (black screen is normal, there will be dots flying after a minute or so to keep you entertained).
Yes, It's that simple nowadays, so why bothering typing so much? I was in that situation with my SP, too, but if the are so many answers to these questions and so many threads... "You have to read" is the answer! A lot! It's for your own good, trust me. Now I can do anything I want with my phone with nohow! So a little reading and searching here and there is just positive experience for you. Don't complain, the people here ( well a part of them) are hardcore coders or themers or whatever. You can't just ask them to tell you all the stuff. If want help I'm always available.
Thank you for linking to my very dusty and lonely Flash ROM guide hahaha
No you didn't offend anyone at all. The guides are actually there, like how to use Flashtool, how to unlock bootloader, how to flash recovery and everything, it is just that they are buried deep with time as the development goes. The thread are there, in the General section and are awaiting to be searched. Though some are outdated, some are not and you can benefit from there.
Some searching will normally do, but if it didn't, just ask in the threads, someone will probably answer to you!
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
About recovery, PhilZ and CWM is way outdated, and its time for everyone to make TWRP as a standard as it is a still updated recovery. Cyanogen Recovery in my opinion is crap as there are far too less feature plus, it enforce on signed flashable zips.
About the thread on Tangerine, the developer said dont use if it doesn't work is because of the norm of the Kernel. The kernel is made by using an AnyKernel template, hence render support for almost all Lollipop ROMs. Since ROMs can be updated and all ROMs have different sources, a simple change in the system part can render Tangerine unsupported, and the developer cannot do anything (definitely his choice, please respect that) to only fix the problem on one ROM which could possibly break support for the majority of the ROMs! This also appplies to Helium. Therefore, his words of "dont user it if it doesn't work" has a meaning, and it is not something to degrade new users and so.
kojata said:
If want help I'm always available.
Click to expand...
Click to collapse
TechnoSparks said:
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
Click to expand...
Click to collapse
Thanks for the answers and offering help, happily I was able to install my ROM of choice and it still works flawlessly, I was even able to squeeze 20 battery days from my old XSP.
Thinking about it, I start to understand why that dev answered like that. I was a python dev in the past and know how one feature can kill two others. Just in my head there is one current linux kernel, and all things that are developed should work with that particular kernel. Kernel comes before OS, if you will. Isn't it the case with ROMs and droid kernels?
About TWRP and reading: I honestly did read a lot of info before doing something, because it's my only phone these days. But it's so hard to find information on whether something is deprecated or not. As a new user, you wouldn't just google "is this deprecated and no longer used?", because that search will not provide any info. That is why during that evening and following morning I lost count of how many times I just shaked my head asking which recovery/kernel should I use and how do I install it? Latest being the easy one, because I already found TechnoSparks thread by that time.
In case anybody is interested, I installed Candy 5 on default kernel. But I still don't know if installing android 5 on a kernel used with android 4.2 was a good idea. It went well, however.