Related
Dear developers,
i hope it is not too offensive, if so it's not my intention, but is there a way to make all your great ROMs compatible for nexus one SLCD!
Maybe you can share in this thread and it will make the development of compatible ROMs easier for you.
Many people would be happy about it.
Having a compatible recovery with RA RECOVYER 1.8.0.1 is more than just the first step.
Unfortunately I can not help you much, because i'm just consumer and no dev.
The issue is that after flashing several ROMs on SLCD the screen after the first splash screen stays black.
CM 6.0.0 is working after changing the update script before flashing.
I want to enjoy the great variety of your ROMs on my nexus one, so please try to help.
Thank you very much for your great work....!
I would just like straight answers.
Does SLCD support just require updated drivers?
Aren't the drivers included on AOSP?
And therefore, any ROM that draws straight from AOSP has the correct drivers?
Is it easier to install a custom ROM that supports SLCD if you have unlocked your bootloader?
Why is amon_RA 1.8.0.1 the only one that supports SLCD?
Why isn't 1.8.0.1 the most recent version available in the amon_RA recovery thread? And not the most current one listed in ROM manager?
You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.
Jack_R1 said:
You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.
Click to expand...
Click to collapse
Do you know which branch in the AOSP includes support for Nexus One SLCD?
I've already tried the froyo branch without any success and android-2.2_r1.1 branch crashes while flashing.
Didn't check the commits since looking for a way to change MMS resolution (and didn't look beyond that ), so I'm sorry, but I'm not the person qualified to answer. Asking someone from CM team or Enomther might be a better idea to find the Google source (since those ROMs have incorporated the support).
Enomther is basing on r1.1, so it should be usable. Never tried to compile myself, so I can't be of help there....
CM has this commit in his github (from pershoot's log):
87f604b7d75e77af62a2074e993a91aa00f1fcf5 ([ARM] mahimahi: add support for Sony TFT panel)
These are 4 repositories that might also hold the commit:
http://htc-linux.org/wiki/index.php?title=Kernel#Qualcomm_QSD8xxxx
Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think
hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!
Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.
So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.
This question is for those who has installed on both bootloaders previously.
[contemplating unlocking the bootloader]
I know that there are more ROMs available (probably shrinking?) for UBL than for LBL.
I also know that, with UBL, I can install other kernels instead of being limited to Sony's.
Other than the 2 reasons stated above, are there any other benefits of UBL?
[e.g. customised kernel is faster, blah, blah blah...]
Thanks for helping.
Not only more ROMs but also more quality.
Lets just say, no barrier for what you want to do.
Locked Bootloader is basically a bootloader that is forced to only boot into a legitimate ROM. With proper hijacking, custom ROMs may be able to boot with the phone with a locked bootloader. Also, a splash of DRM keys added towards it.
For warranty comparisons, it is much easier to have a LBL, in case of damage and you want to send to service centre all you need to do is a quick flash through Flashtool and you are done. Unlike unlocked bootloaders, your warranty was already void. Or if you have backup, you would have to add 2 more steps to the process.
The thing I like the most with UBL is you can do anything. You can even flash an LBL ROM and use it without any problems at all. Risk of bootloops are significantly less compared to the LBL, though this is solely depends on what you do to the device.
Hve unlocked my XSP this weekend and experimented with a few roms plus cm11 latest nightlies
Yup - it has a big advantage in that the many new roms are available to the XSP. My interest was in CM12 and lollipop.
[but alas, to my dismay, my initial feeling is that CM12+lollipop is 'laggy' compared to plain vanilla CM11 (no CM12 vanilla at the moment for XSP).
One further advantage with vanilla CM11 in UBL - OTA
I got the nightly from early May, and, with a button, it updated me to the one on 10th May.
At this point in time, I think almost all of XSP owners should have unlocked - because the XSP is 'outdated' (at least in my country), and warranty would have expired. Save for those with unlockable bootloader, of course.
headache59 said:
Hve unlocked my XSP this weekend and experimented with a few roms plus cm11 latest nightlies
Yup - it has a big advantage in that the many new roms are available to the XSP. My interest was in CM12 and lollipop.
[but alas, to my dismay, my initial feeling is that CM12+lollipop is 'laggy' compared to plain vanilla CM11 (no CM12 vanilla at the moment for XSP).
One further advantage with vanilla CM11 in UBL - OTA
I got the nightly from early May, and, with a button, it updated me to the one on 10th May.
At this point in time, I think almost all of XSP owners should have unlocked - because the XSP is 'outdated' (at least in my country), and warranty would have expired. Save for those with unlockable bootloader, of course.
Click to expand...
Click to collapse
Glad you are happy for unlocking your Xperia SP!
XSP is indeed outdated especially here in Malaysia. About warranty, lol I forget about it after 3 months of buying the phone haha
i prefer unlocked bootloader becasue it lets me install custom kernels...
UBL doubt
What if, after unlocking, I loose my IMEI code is or s/n code after flashing?
Also is there anyway to retain it and make my xsp as a new phone, (not physically)( as softercally)
Hey guys, I suppose some of you have had a xiaomi in the past and I have two questions for you and maybe someone that has some knowledge about xiaomi.
1) Currently how's Xiomi dealing with privacy? I remember 1 or 2 years ago Xiaomi has hit with strong reports of leaking information to their government (chinese) and everything we did on the phone would be seeded to their servers, even SMS's and other stuff..
2) How's the ROM support usually for Xiaomi? Do they usually get a stock based ROM, which has no bloatware and some nice tweaks?
Thanks everyone!
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
arnabbiswasalsodeep said:
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
Click to expand...
Click to collapse
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
SlyUK said:
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
Click to expand...
Click to collapse
There will sure be support for custom roms even when the kernel source isn't there, my device had custom roms even before kernel source was released, although there were a bit bugs due to it and only a few (like 5 to 10) custom roms were there, bit with the release of sources, it jumped to 50+. And my device had the bootloader unlocked by default, which even i didn't knew until i rebooted to it. Although the fastboot wasn't able to get the info about the bootloader (like version, etc). IDK if any new devices require to unlock it but i don't think it should be hard as they support it, so that won't be a barrier for development.
TL;DR- less n buggy roms w/o kernel source, floods of roms and custom kernels after source, nothing to concern about bootloader.
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
zelendel said:
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
Click to expand...
Click to collapse
With regards to porting an official rom, I suppose these would be regarded as Unofficial versions. If that is the case is there any real disadvantage in having the "Port" as opposed to have the "Official" version ?
Ports normally will have some bugs as this happens due to not having some things for device built into the code.
Data leak & Software development
Yes I also heard that even with a custom ROM on the device they still found a way to make the device connected and synching information with their servers, which I don't find that funny..
I wanted to know if this data leak is still present in the previous flagship, anyone tested it recently?
It's good to know that it has nearly no bloatware from what you are saying me, but if it has something I don't find useful I may just freeze the app.
Also does anyone know if Xiaomi usually takes long times to update the software of their devices (I heard that they were an exception in relation to other Chinese manufacturers) and release the kernel sources for the ROM developing community or are they pretty good on this area?
Thanks!
:good: :good: :good:
No they are terrible about it. Normally when they post the kernel source it is incomplete and broken.
As for updating. Until very recently they based their os on 4.4 and when asked why they said they didn't care about official android versions.
As for bloat that depends on how you look at it. Miui is about as bloated as TW or HTC Sense.
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
SlyUK said:
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
Click to expand...
Click to collapse
The biggest are the one or two devices (cant remember their names off the top of my head) that were able to get/fix the kernel source and device trees which CM picked up. So some of the teams that use CM source as a base like AICP also picked up Official versions for the devices.
Then you have the Roms that are based on AOSP instead of CM. As they dont use CM as a base ( Maybe some parts) These roms like Slim or Dirty Unicorns seldom see official versions of the rom. Normally you might get a port here and there. It all depends on if the one of the devs gets the device as most teams don't offer official support for devices they do not own.
dear Master,
previously i own xperia go and M. both of them are bootloader unlocked.
now im using z3 compact. i heard that if i unlock the bootloader it has effect on quality of picture. when i have Go and M. i cant differentiate the quality of pic.
so my question is, is woth unlocking bootloader on z3 compact?
for me - No
for many - Yes
Well yes, that you can get cyanogenmod and many other great ROM's (Cyanogenmod has a great battery life and great enhancements), plus great kernels.
But no, if you enjoy using your phone for photography, then do not unlock it.
As unlocking your bootloader, you loose your DRM keys (which enhance photography, visuals and sound of the Xperia.
If I were you, I would wait until after stock Marshmallow is released and give it a try via standard, factory OTA. If MM were still months away, I wouldn't wait.
Then, after you've gotten tired of stock MM and its features, and you want to try new things, take care to back up your DRM keys (which is a bit tricky; you have to root without unlocking, I believe). After you've done that and have backed up your data, as long as you're careful and follow the more detailed tutorials on this forum, you can experiment to your heart's content.
Could we root z3 compact without unlocking bootloader? I have an unlocked bootloader z1 compact and yes it does effect the picture quality. All those 3rd party OS's can't match stock camera quality. Period.
Yes You can see here: http://forum.xda-developers.com/showthread.php?t=3011598
giefroot - rooting tool (CVE-2014-4322)
Now if worth or not unlocking it depends if you want another thing then stock or stock based. But till now there isn't to many choices... So stock with root for many is enough I think...
I unlocked bootloader but can restore the cam quality. Google "drm restore xperia xda". Sorry i'm on mobile cannot provide link.
So, go unlock it!
I downgraded my phone to 4.4.4, root exploiting, install XZDualRecovery and flash pre-rooted firmware
duke_dreadmoore said:
I unlocked bootloader but can restore the cam quality. Google "drm restore xperia xda". Sorry i'm on mobile cannot provide link.
So, go unlock it!
Click to expand...
Click to collapse
Hey, just a single question for you please. I am on KitKat rooted and locked bootloader. Can I flash Sony Concept Marshmallow and then restore DRM keys to make sure that Noise Cancellation and camera works good?
HearseRider said:
Hey, just a single question for you please. I am on KitKat rooted and locked bootloader. Can I flash Sony Concept Marshmallow and then restore DRM keys to make sure that Noise Cancellation and camera works good?
Click to expand...
Click to collapse
Yes, but why would you want to do that?
There are several Marshmallow builds out now that are stock. Far less hassle. Sorry, but any development that insists on recking the best features of your camera doesn't get my vote.
You just need Flashfire and Slim, then your phone will be amazing
thanks all master, and friends.
i just got back my z3 compact. after had screen cracked by it self. fortunately it still has warranty. it take 3 months. hahahaha
Didgesteve said:
Yes, but why would you want to do that?
There are several Marshmallow builds out now that are stock. Far less hassle. Sorry, but any development that insists on recking the best features of your camera doesn't get my vote.
You just need Flashfire and Slim, then your phone will be amazing
Click to expand...
Click to collapse
You are aware that the DRM restoration mod enables all those camera features even after unlocking a bootloader, right? I have my original DRM keys backed up and my bootloader unlocked for a year already and haven't looked back since, because everything is easier with BL unlocked + custom kernels (@someone755 gave us a very appealing MM kernel) and with the DRM restoration working on all stock based roms (from KK to latest MM, Concept rom included) it's a pure joy.
Plus, he can use MultiROM and boot CM/AOSP based rom, to experience stock Android, with the noice reduction algorithm working EVEN on **CM/AOSP, confirmed as well.
**Do note that it's not working wonders as on stock, but it is noticeable difference compared to using CM/AOSP as primary rom, without MultiROM.
Anyway at this point in development, since there is no difference between features (camera) of locked BL vs unlocked BL with DRM restoration mod, it all comes down at how easier it is to flash custom recovery and roms with UBL.
That being said, we all have different preferences, so what suits my needs does not necessarily suit someone else's, and if the OP is asking it just for the sake of having his bootloader unlocked (without the need to flash CM/AOSP rom and/or custom kernel) then don't do it. If OP wants to flash and experiment, then just go ahead and unlock.
Read the needed tutorials, find a tutorial to root the device without unlocking BL, BACKUP ORIGINAL DRM keys right away after rooting, and do as you wish
Cheers
P.S. @Didgesteve Don't get mad mate, not flaming you, just giving the OP choices and additional info, like yourself, and I support your helpful posts as I've seen your dedication
Cirra92 said:
You are aware that the DRM restoration mod enables all those camera features even after unlocking a bootloader, right? I have my original DRM keys backed up and my bootloader unlocked for a year already and haven't looked back since, because everything is easier with BL unlocked + custom kernels (@someone755 gave us a very appealing MM kernel) and with the DRM restoration working on all stock based roms (from KK to latest MM, Concept rom included) it's a pure joy.
Plus, he can use MultiROM and boot CM/AOSP based rom, to experience stock Android, with the noice reduction algorithm working EVEN on **CM/AOSP, confirmed as well.
**Do note that it's not working wonders as on stock, but it is noticeable difference compared to using CM/AOSP as primary rom, without MultiROM.
Anyway at this point in development, since there is no difference between features (camera) of locked BL vs unlocked BL with DRM restoration mod, it all comes down at how easier it is to flash custom recovery and roms with UBL.
That being said, we all have different preferences, so what suits my needs does not necessarily suit someone else's, and if the OP is asking it just for the sake of having his bootloader unlocked (without the need to flash CM/AOSP rom and/or custom kernel) then don't do it. If OP wants to flash and experiment, then just go ahead and unlock.
Read the needed tutorials, find a tutorial to root the device without unlocking BL, BACKUP ORIGINAL DRM keys right away after rooting, and do as you wish
Cheers
P.S. @Didgesteve Don't get mad mate, not flaming you, just giving the OP choices and additional info, like yourself, and I support your helpful posts as I've seen your dedication
Click to expand...
Click to collapse
@Cirra92 you're right, it's good to give people choices. & no I'm not mad.
But development is limited on our aging Z3Cs, I know you mention CM & AOSP roms, but really there aren't any working well to speak of.
The only couple of developements with any traction is Slim or Concept (Max Ultra Fury is just bits of scripts copied from other deveolpers). So if you had to recomend which one to choose and one of the options involed unlocking the bootloader, which one would you go for?
I know there's a way to restore your DRM post unlock, but having spent a while on the Z3 thread, I've seen so many cries for help (like here & here & here & here) from people who get it wrong and brick their phones with Flashtool, that I struggle to recomend people playing with the tool when the stock options are just as good and won't endanger the phone.
Didgesteve said:
@Cirra92 you're right, it's good to give people choices. & no I'm not mad.
But development is limited on our aging Z3Cs, I know you mention CM & AOSP roms, but really there aren't any working well to speak of.
The only couple of developements with any traction is Slim or Concept (Max Ultra Fury is just bits of scripts copied from other deveolpers). So if you had to recomend which one to choose and one of the options involed unlocking the bootloader, which one would you go for?
I know there's a way to restore your DRM post unlock, but having spent a while on the Z3 thread, I've seen so many cries for help (like here & here & here & here) from people who get it wrong and brick their phones with Flashtool, that I struggle to recomend people playing with the tool when the stock options are just as good and won't endanger the phone.
Click to expand...
Click to collapse
I have been using SliMM 2.0 and it was fast and mostly reliable (Wajk has made sure to make it stable) but there were still some bugs, and battery life for me was a bit worse than his LP rom with same usage and setup. If OP requires root on whatever rom he chooses, I would go for Concept (which does require UBL to be rooted) as it's the fastest I've used, it's stable as a rock and it has a very good battery life + it's nearly AOSP looking and performs that way.
As for the Flashtool issues... Well if I understood those were mostly user mistakes, right? I have always carefully checked what was (un)selected before flashing anything in Flashtool, especially with SIMLOCK. When I bought the device last summer I probably spent 2 days reading every thread about rooting/(un)locking/flashing and it's consequences and even today I still recheck and read again the procedure if needed.
Follow the tutorials exactly as they were written and no problems will occur
Cirra92 said:
I have been using SliMM 2.0 and it was fast and mostly reliable (Wajk has made sure to make it stable) but there were still some bugs, and battery life for me was a bit worse than his LP rom with same usage and setup. If OP requires root on whatever rom he chooses, I would go for Concept (which does require UBL to be rooted) as it's the fastest I've used, it's stable as a rock and it has a very good battery life + it's nearly AOSP looking and performs that way.
As for the Flashtool issues... Well if I understood those were mostly user mistakes, right? I have always carefully checked what was (un)selected before flashing anything in Flashtool, especially with SIMLOCK. When I bought the device last summer I probably spent 2 days reading every thread about rooting/(un)locking/flashing and it's consequences and even today I still recheck and read again the procedure if needed.
Follow the tutorials exactly as they were written and no problems will occur
Click to expand...
Click to collapse
Perhaps we can agree to disagree.
I don't think telling someone who's new to XDA and only has a handful of posts that they should embark on the unlock process. Some phones can't be unlocked and I am tired *sigh* of trying to comfort users who post the "waaa, my phone is broken", over and over again.
Hey all....experiencing lag and overheating after unlocking BL .Is that ok ,anyone?
Using slimm 2.4 full rom on my D5803 .Factory reset and drm fix applied ,prior use
nicorb said:
Hey all....experiencing lag and overheating after unlocking BL .Is that ok ,anyone?
Using slimm 2.4 full rom on my D5803 .Factory reset and drm fix applied ,prior use
Click to expand...
Click to collapse
My bootloader is locked, sorry, can't help you.
Perhaps @Cirra92 might have some ideas?
Unlocked bootloader on Xperia Z5, rooted with stock MM rom (253). Debloated and deodexed, and get easily over 8hrs of SOT (screen on time) with still about 20-24% battery remaining .. So is it worth it?? You tell me ..
***In other words, YES***
Only if you know what you're doing so you dont hard brick your device
Hope that helps, All the best ....
Sent from Sony Xperia Z5 E6653
nicorb said:
Hey all....experiencing lag and overheating after unlocking BL .Is that ok ,anyone?
Using slimm 2.4 full rom on my D5803 .Factory reset and drm fix applied ,prior use
Click to expand...
Click to collapse
Nope, that won't be caused by unlocking your BL. I've flashed different roms numerous times, no such issue. Haven't tried slimm 2.4 though, maybe it is rom related, but so far no one mentioned that. You are using stock slimm kernel, right?
Install Kernel Adiutor from Play Store and check which governor your device is using in CPU section. It should be "interactive", but there are cases where it was set to "performance" after unlocking BL, which caused overheating and lagging due to thermal throttling.
To answer again, is it worth unlocking, from my point of view