Database Users

[samsung i857(doubletime)]ROM devlopers and users of this phone

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

Windows OS from new Verizon m8?

Do you think it will be possible to port the windows OS onto our phones? Thinking of a possible dual boot option.

This thread closes in
1..
2..
3...

Thread closed,
Please search before posting. We have closed a number of these threads already as there is no definite release information as yet.
Many thanks,
GHost

Regular updates for omni-4.4.4 (FINAL)

Hi there,
I've recently updated my tablet to a custom ROM for the first time and this is my first post here, so please correct me right away if there is a better place for asking such kind of questions.
My question is specifically about omni-4.4.4 (FINAL). For now I'm not interested in the 5.1.1 branch (NIGHTLY) at all, as I'm looking for stability.
So the question: is there any kind of update policy for the OMNI-4.4.4 branch? In the light of the recently published security flaws in Android, I'd like to know more about my options. I don't mind to try to build the rom myself, provided that the source code in the branch is updated regularly.

Stagefright-Bug-Fix for Galaxy Nexus Kitkat 4.4.4 (post #2) answers the question about the forthcoming update.
Good to know that "FINAL" doesn't mean that support for the branch is over.
Entropy512, do you make any kind of announcement after the source code has been updated? I'm just wandering what is the best way to follow the process.

pordzi said:
Stagefright-Bug-Fix for Galaxy Nexus Kitkat 4.4.4 (post #2) answers the question about the forthcoming update.
Good to know that "FINAL" doesn't mean that support for the branch is over.
Entropy512, do you make any kind of announcement after the source code has been updated? I'm just wandering what is the best way to follow the process.
Click to expand...
Click to collapse
We'll make some sort of announcement when it happens.
I have the day off Friday and will hopefully be far enough ahead in the apartment-cleaning process to work on this.

Cyanogenmod 13.1 for Axon 7... When?

Checklist of Things to Do w/ Axon 7
1. Unlock Bootloader - DONE
2. Flash TWRP - DONE
3. Get Root Access, along with Root apps - DONE
4. Flash Cyanogenmod 13.1 - PENDING
Who is interested in seeing Cyanogenmod 13.1 running on the ZTE Axon 7 as much as I am? If so, please post on this thread. Hopefully, the right people will check this out and get the ball rolling on this project.

Why don't you build it ? ?
We are never happy ... let the devs work ... on the other hand they have a life and bills to pay !
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app

like tupirujp says.
If you want your question answered just contact Cyanogen directly.

***Thread Cleaned*** (removed negative, counterproductive comments/quotes, for a fresh start)
Some concerned users brought this thread to the attention of Moderation staff.
A good practice is to have the dev needing the device (Unjustified Dev) set up their own donation link, express their desire to dev for the device, and put out a little description of the work they intend to do for that device (ie; unlock bootloader, Roms , Kernels, etc)...
Otherwise, third party donation links usually only raise suspicion, mistrust, and rarely accomplish the goal of helping the dev get a device.
I applaud those who want to support developers (they certainly deserve the support), let's make sure we do it in a way that isn't counterproductive to the goal or the donation process.
Thanks for your cooperation.

Well, in order to build a rom you need:
Device Tree
Kernel
Vendor/Proprietary files
We have versions of the first two already loaded on GitHub. It's a (hard) matter of someone figuring out what proprietary files we need and then going through the iterative testing to ensure all the hardware components are working. So, let the devs have time with the phone to see what they can figure out and we'll start seeing development.

Please Cyanogenmod come to this device..

Advice on Purchase

Hello,
I'm strongly considering picking up a LePro 3, but I do have some concerns. I understand that the stock software isn't very good and I'm looking towards the community to create excellent ROMs for this device, but I do have some questions:
Do we have a clean method for root/unlock/recovery?
Is there anything stopping developers from putting together ROMs that are optimized for every aspect of the phone? i.e. enough source from LeEco?
How would you say developer support is for this device? I'm a fan of official ROM builds instead of using unofficial. Has anyone announced upcoming support for this device that I can look forward to?
Aside from that, feel free to mention anything else I should be aware of before purchasing the phone!
Thanks so much!

Do we have a clean method for root/unlock/recovery?
I have no idea what you mean by clean but if you can use adb then yes we do. If you are looking for a one stop shop all in one unlocker then the answer is no. look here for current method:
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
Is there anything stopping developers from putting together ROMs that are optimized for every aspect of the phone? i.e. enough source from LeEco?
I believe all source code has been released.
How would you say developer support is for this device? I'm a fan of official ROM builds instead of using unofficial. Has anyone announced upcoming support for this device that I can look forward to?
There is minimal development currently. One person is trying to build a Nougat 7.1 Rom. That's a pretty big feat so it will probably be a while. Look here:
http://forum.xda-developers.com/le-pro3/how-to/7-1-progress-t3511474
There is a developer that posted a debloated version of the x720(international version) of this rom already. It will work on our x727(US version). It is an older version though so there's that. Look here:
http://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742
xiton said:
There's a CM 13 rom here based on the chinese x720. Look here:
http://forum.xda-developers.com/le-pro3/how-to/cm-13-lex720-t3508015
Aside from that, feel free to mention anything else I should be aware of before purchasing the phone!
This is literally the smallest compilation of threads I've ever seen for a phone so starting a new thread to ask these questions is pretty silly. Since it's the holidays, I've been nice and responded to what could have easily been found in a couple of minutes.
Click to expand...
Click to collapse

Thanks for the reply.
The reason I compiled these questions were because I was hoping for more specific answers and some clarity. Perhaps I wasn't clear enough my initial post and for that I apologize.
I was reading what seemed to be conflicting information about the recovery software and process in which to flash it to the device. It looked as if there wasn't any goto method or specific TWRP version to go with and that this was still somewhat experimental.
It's good to know that the source has been released. I was seeking info about LeEco and people were saying that they didn't release source code for their phones as company policy.
While I've visited the ROM forum section, I was hoping someone would have insight into official ROMs instead of what currently exists there.

For the US model Le Pro 3 (X727) I would recommend using this (http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388) method to unlock the bootloader. That's what I did and had no issues. From there you can use TWRP to do a full wipe and install the ROM of your choice. Of course, I would recommend taking a backup of everything before doing this.
I'm running that CM 13 build with no issues on my X727. It's also possible to get the IR blaster working if desired.