Related
I really enjoy the screen lock/screen unlock animation present on stock ICS such as the Galaxy Nexus (old TV style shut down basically). I was wondering if anyone knows of a way to put this on the HTC One X? If you do it would be greatly appreciated!
not yet, i believe we need the kernel source first
bloodrain954 said:
not yet, i believe we need the kernel source first
Click to expand...
Click to collapse
Tis unfortunate that its taking so long to be released. Thanks for your response!
AOKP actually has this right now (Which means CM9 Alpha 5 does too)
Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?
Hm. I might take a shot at this. Though I personally prefer 4ext
devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.
My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3
VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away
I'm interested in getting the stock rom (the zip like paranoidandroid) but I can't seem to find where to get it. I'm wanting to create a custom ROM with it, but that's not going to work without the zip.
Hi,
[ROM] [STOCK] Android 4.4.2 KOT49H.
[ROM] [KOT49H] Pure Stock // Odex + Deodex // UNTOUCHED .
[ROM] Stock Nexus 5 ROM KOT49H Android 4.4.2.
Stock roms (made by Google), flashable zip files, see the explanantion by @rootSU
pyrogoggles said:
I'm interested in getting the stock rom (the zip like paranoidandroid) but I can't seem to find where to get it. I'm wanting to create a custom ROM with it, but that's not going to work without the zip.
Click to expand...
Click to collapse
Your question doesn't make sense.
AOSP is AOSP
Stock is Stock
Stock is not AOSP
AOSP is not Stock
Paranoid Android is not Pure AOSP.
What EXACTLY do you want?
rootSU said:
Your question doesn't make sense.
AOSP is AOSP
Stock is Stock
Stock is not AOSP
AOSP is not Stock
Paranoid Android is not Pure AOSP.
What EXACTLY do you want?
Click to expand...
Click to collapse
Ouch, I see where I went wrong with that question.
When you download Paranoid Android, you get a .zip file that you can flash to your device.
I'm wanting to create a new ROM off of the stock Hammerhead ROM. How would I get a zip file that contains the files, like paranoid android or cyanogenmod. Hopefully this question is easier to understand.
Hammer_Of_The_Gods said:
Hi,
[ROM] [STOCK] Android 4.4.2 KOT49H.
[ROM] [KOT49H] Pure Stock // Odex + Deodex // UNTOUCHED .
[ROM] Stock Nexus 5 ROM KOT49H Android 4.4.2.
Stock roms (made by Google), flashable zip files, see the explanantion by @rootSU
Click to expand...
Click to collapse
Thanks!
If you are in any way serious about it, you should download and and build from source instead.
pyrogoggles said:
Ouch, I see where I went wrong with that question.
When you download Paranoid Android, you get a .zip file that you can flash to your device.
I'm wanting to create a new ROM off of the stock Hammerhead ROM. How would I get a zip file that contains the files, like paranoid android or cyanogenmod. Hopefully this question is easier to understand.
Click to expand...
Click to collapse
Oh I see. There's not much that can be edited in a stock ROM easily. As mentioned, compiling from source gives the most customisation.
I believe most stock ROMs are edited in DSI XDA kitchen from a Nandroid backup.
Sent from my Nexus 5 using Tapatalk
I'm afraid I'm only building for Hammerhead. Down the line, when I get a spare PC, I'll get the actual source.
I'm going to set this up on a VM when I get home. Thanks very much for the help.
pyrogoggles said:
I'm afraid I'm only building for Hammerhead. Down the line, when I get a spare PC, I'll get the actual source.
Click to expand...
Click to collapse
Eh? If you're not using source, you're not building at all. ...and the source is designed for hammerhead, yes.
I see. Know of any tutorials on how to fetch the source for Hammerhead from the right place? Sorry if it seems I'm giving a run around, I'm new to it.
pyrogoggles said:
I see. Know of any tutorials on how to fetch the source for Hammerhead from the right place? Sorry if it seems I'm giving a run around, I'm new to it.
Click to expand...
Click to collapse
Yeah in this thread is a link:
http://forum.xda-developers.com/google-nexus-5/help/how-to-compile-aosp-nexus-5-t2720556
Warning, there was an issue with time on boot up, but if you read the whole link above, at they end the OP solved it.
ZIP To Completely Unaltered Build OF AOSP.
pyrogoggles said:
I'm interested in getting the stock rom (the zip like paranoidandroid) but I can't seem to find where to get it. I'm wanting to create a custom ROM with it, but that's not going to work without the zip.
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/general/guide-how-to-build-aosp-source-linux-t2703036
At the top of my guide is a zip to a completely stock unaltered build of AOSP.
pyrogoggles said:
I'm afraid I'm only building for Hammerhead. Down the line, when I get a spare PC, I'll get the actual source.
Click to expand...
Click to collapse
youre not building at all, lol. youre trying to get a base rom then edit it to become a different rom with different features. you cant do that, you need to build it how you want it.
Hi, I tried the XDA Assist board and was redirected here so I was wondering if anyone here knows how to modify the Battery Animation in the Powered Off State, currently on my current ROM (BrokenOS 1.4 Official 4.4.4) the animation is gone and is just a static image so I'm unable to tell if the battery is charging/battery level.
I found the stock images in the res/images/charger and that's not at all what I currently have with this ROM and I'm unable to find the ones I do have. Is this a glitch on my part and if so how do I fix this, I really like charging my phone while off so that it can rest.
Below is the image of what I currently have,it just looks like a fat cigarette too me which urks me...
http://forum.xda-developers.com/attachment.php?attachmentid=3061739&d=1418452145
Device Info (Incase it Helps)
Verizon Samsung Galaxy S3 - BrokenOS 1.4 (Official 4.4.4) - BMS (Kernel) - SuperSU 2.3.7 Pro - TWRP 2.8.1.0
Anyone have a idea of what direction to go in to resolve my problem?
I still haven't figured a solution to this,anyone?.. any enlightenment on this?
RyanEsau said:
I still haven't figured a solution to this,anyone?.. any enlightenment on this?
Click to expand...
Click to collapse
Maybe it's the rom not the file itself?
From my CM11 S3
ShapesBlue said:
Maybe it's the rom not the file itself?
From my CM11 S3
Click to expand...
Click to collapse
I'll try that out real quick and reply back, if it is the ROM is there anyway to resolve that?
RyanEsau said:
I'll try that out real quick and reply back, if it is the ROM is there anyway to resolve that?
Click to expand...
Click to collapse
That would be a bug issue with the rom. Have you tried using rom toolbox pro? That's of course if you have it... It's been known to work with RTP
From my CM11 S3
ShapesBlue said:
That would be a bug issue with the rom. Have you tried using rom toolbox pro? That's of course if you have it... It's been known to work with RTP
From my CM11 S3
Click to expand...
Click to collapse
I do have ROM Toolbox Pro, I use to use it but I stopped using it since I mainly just used (at the time) for Restart System UI on my previous phone. Is something in RTP that would fix the issue?
RyanEsau said:
I do have ROM Toolbox Pro, I use to use it but I stopped using it since I mainly just used (at the time) for Restart System UI on my previous phone. Is something in RTP that would fix the issue?
Click to expand...
Click to collapse
It has built in boot animations. Well not built in but ones you can download and flash through recovery via RTP
From my CM11 S3
ShapesBlue said:
It has built in boot animations. Well not built in but ones you can download and flash through recovery via RTP
From my CM11 S3
Click to expand...
Click to collapse
Alright, well I just flashed my previous ROM I was using (BlissStalk) alongside all my other things I would flash and it works, so I'll try flashing the ROM (BrokenOS,what I was using) standalone and see if it reoccurs. Might switch ROMs if it really is the ROM,there was features in BlissStalk that BrokenOS doesn't have. (Power Widget for one, I had just learnt to dealt with the Toggles and use Quick Pulldown)
RyanEsau said:
Alright, well I just flashed my previous ROM I was using (BlissStalk) alongside all my other things I would flash and it works, so I'll try flashing the ROM (BrokenOS,what I was using) standalone and see if it reoccurs. Might switch ROMs if it really is the ROM,there was features in BlissStalk that BrokenOS doesn't have. (Power Widget for one, I had just learnt to dealt with the Toggles and use Quick Pulldown)
Click to expand...
Click to collapse
Definitely worth a shot. Anymore problems feel free to PM or just post here
From my CM11 S3
[RESOLVED]
Talked further in PM and resolved my problem. Thanks to ShapesBlue for the assistance..
Might try BrokenOS again when/if they update, sticking to BlissStalk for now.
Since Oxygen is out for Oneplus one is anyone porting this soon to our phone? It has built in DT2W and other gestures
Gestures are done with the kernel, not the ROM.
Porting the ROM as a whole is ultimately pointless - just use any custom ROM, which probably has all the features + more anyways.
Elluel said:
Gestures are done with the kernel, not the ROM.
Porting the ROM as a whole is ultimately pointless - just use any custom ROM, which probably has all the features + more anyways.
Click to expand...
Click to collapse
But i think it would be nice to have both OxOS and Cm12S to our phones. Im sure both will be ported soon even know one is based off of 5.0.2
cell2011 said:
But i think it would be nice to have both OxOS and Cm12S to our phones. Im sure both will be ported soon even know one is based off of 5.0.2
Click to expand...
Click to collapse
Also, see my quote below.
Elluel said:
First of all, porting firmware from one device to another is extremely unlikely to function properly. If you can even get it to boot (the hardest part), a LOT will be broken as it was not built relevant to the hardware. Porting a custom ROM is even more pointless when it can be built specifically for your device.
OxygenOS has not been released yet, but it's likely to have features that other custom ROMs already have/can easily replicate.
Porting "CM12S" from the OnePlus One to the Nexus 5 is ultimately pointless. CM12 can be built from source anyways, then you can just take the few additional extra apk files from CM12S and paste them in.
Click to expand...
Click to collapse
Rom Port
cell2011 said:
But i think it would be nice to have both OxOS and Cm12S to our phones. Im sure both will be ported soon even know one is based off of 5.0.2
Click to expand...
Click to collapse
Can you point me the rom port download link please
joaopaulomachadooficial said:
Can you point me the rom port download link please
Click to expand...
Click to collapse
It is not available yet. Also, this thread is a bit old.
its an old thread, was reading about this as opo 2 is coming out, from what i read if that its not open sourced and there is a small team doing the build, the kernel will be open, i wonder how they will manage without the community