Database Users

[HELP/BETATESTERS NEEDED] ShishirROM i9100

Hey there guys
I'm a dev from the i777 forum -- the AT&T Version of the i9100. My rom, ShishirROM, is based off of XWLPG Odexed -- one of the few i777 ROMs to be odexed. It revolves around having great battery life and stability, as well as being nicely polished and revolving around JKay's brilliant mod.
The page can be found here: http://forum.xda-developers.com/showthread.php?t=1505433
Okay, so I need YOUR help to port this ROM over the i9100. It should be very straight-forward, but I'll need a few beta-testers to make sure everything works as advertised. And being a i777 user, I need to know a couple of things to make sure the ROM is perfect out-of-the-box:
What are the most stable/fastest i9100 modems and kernels?
That's it for now, and I'll need some willing beta testers to PM me with:
Experience modding/testing
Ability to use adb / analyze logcats
Has plenty of backups of existing ROMs incase something goes wrong
Has plenty of time to beta-test
I can only take around 3 or 4 of the most qualified since I don't intend to have to give instructions with each package (e.g., adb push file to directory then chmod, etc.). I think this is the first time someone has tried to port an i777 ROM to the i9100, but I know it's possible and I could make the necessary changes and upload it right now, but I'll need to make sure it works first.
Thanks

[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

I see a pattern emerging - lack of guides

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.

REQ rooted kernel 5.1.1 for Sm-t235 (source was published a month or two back)

sometime back this was posted
http://forum.xda-developers.com/showpost.php?p=63556533&postcount=135
unfortunately moonbutt closed his thread just when I and another member posted boot image etc on the board..understand he may have moved on to better things
not knowledgeable here but appreciate if someone can take this up or redirect this to some dev who can make a rooted kernel since the source has been published
thanks

SM-T237P
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.

OKAY so now I know my posts were getting deleted when I asked for T235 kernel root
zitomd said:
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.
Click to expand...
Click to collapse
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)

mac231us said:
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)
Click to expand...
Click to collapse
mac,
i had your post removed because it was interfering in H's thread. I tried with this device a little while ago but testers seem to think they are at liberty to not follow instruction, or just change their minds mid-stream like they haven't just wasted my time and resources. . The upside would be if you have the source and the setup to compile it and thereby test your own work then, i can absolutely run you through what you need to do, The tricky part is knowing which tools you need for the packing/unpacking of the ramdisk.
If this is a qcom/msm device you will need AIK which is the best solution.
If this is a marvell variant you will need ketut's degas bootimg toolkit which is the best solution.
You need [likely] to apply the patch mentioned in my thread to security/selinux/selinuxfs.c
Be aware that samsung's source releases are usually incredibly sloppy and the defconfigs for devices are usually somewhat off, missing config settings.
Check for sdcardfs xattrs, virtual xattrs, etc . you need to make sure those are selected in order for your internal and external storage to mount.
Find the correct defconfig for your device and post it as a zipped attachment. or check my thread and look at my sources on git, specifically the commit history [msm devices mostly] to get an idea of what you need. You can get a linux os running in a virtual machine and compile just fine as long as you have all the pre-requisites installed. The getting started link in my signature is a rough/general guide to help get you up and running.
m
ps, my thread is just locked, not closed, i was getting too many OT/non-dev postings. I open it when/if i have something new and then close it again.

thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)

mac231us said:
thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)
Click to expand...
Click to collapse
mac,
no prob, recommended step 1, get your linux distro set up, stongly recoommend kali/debian 2.0, either in vm or better as 2nd os in a dual boot scenario.
m

Custom OxygenOS

Since previous development thread was closed, I've been getting a lot of pms. Everyone thanks for the kind words and for offering me help. Thumbs up for this great community.
The reason I didn't post the link was because my laptop or my upload server let me down. At least that is what I saw when I woke up.
No big deal, thought I would upload it upcoming weekend. But as we all might know, today oos 2.2.1 was released. My custom oos was based on 2.2.x, so I was thinking to rebuild this rom again based on the latest software. Meaning it will take a couple of weeks before it will be ready.
So far this briefing. If you have questions regarding this rom, for now please ask in this thread.
Link to original thread:
COSX

To the features, just add the viper4android... And try to make the files app show the root directory too.

I feel you should post ur 2.2.1 build directly when its ready..take your time and i do support what u stand for!! and if possible add network speed indicator

Since there was no answer to this on the original thread, what do you mean by theme support? Layers?

I'll be patiently waiting for your release
But, for playing purpose, are there any guide somewhere to create a moded rom from a stock rom ?
I've been looking but all i could find was from 2012
I don't think it's as simple a remove/add apks from the rom zip :cyclops:

Request
Please donot remove the stock oos camera which has manual focus iso exposure .... __/\__ please