• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root i love you devs. relatedly, any phone with identical hardware that could be used on the sequent?

W

wolfemcbane

Newbie
I was just wondering if maybe the warp sequent is maybe a rebranded phone from another country or something where there has been more work with ROMs etc? if nobody knows then I am just going to make a spreadsheet of the specs and do some detective work. if I find anything I will report back
 
You are going to have a problem with the cameras, bluetooth, touchscreen, and wifi, however I would assume that most any MSM8655 designed ROM would at least boot.

If you can figure out the cameras and bluetooth, feel free to clue a few of us in. We're working on AOKP/CyanogenMod and are having one terrible go at it.
 
bobdamnit said:
You are going to have a problem with the cameras, bluetooth, touchscreen, and wifi, however I would assume that most any MSM8655 designed ROM would at least boot.

If you can figure out the cameras and bluetooth, feel free to clue a few of us in. We're working on AOKP/CyanogenMod and are having one terrible go at it.
Click to expand...

Well, the cameras are Qualcomm cameras, so that's the issue with those. Here's the logcat from Stock B09:

[HIGH]E/QualcommCamera( 138): Qint android::get_number_of_cameras(): E
I/QualcommCameraHardware( 138): getCameraInfo: IN
I/QualcomMCameraHardware( 138): getCameraInfo: loading libqcamera at 0xb000f280
V/QualcommCameraHardware( 138): Storing the current target type as 5
I/QualcommCameraHardware( 138): getCameraInfo: numOfCameras = 2
I/QualcommCameraHardware( 138): Camera sensor 0 info:
I/QualcommCameraHardware( 138): camera_id: 0
I/QualcommCameraHardware( 138): modes_supported: 5
I/QualcommCameraHardware( 138): position: 0
I/QualcommCameraHardware( 138): sensor_mount_angle: 0
I/QualcommCameraHardware( 138): Camera sensor 1 info:
I/QualcommCameraHardware( 138): camera_id: 1
I/QualcommCameraHardware( 138): modes_supported: 5
I/QualcommCameraHardware( 138): position: 1
I/QualcommCameraHardware( 138): sensor_mount_angle: 0
V/QualcommCameraHardware( 138): getCameraInfo: dlclose(libqcamera)
I/QualcommCameraHardware( 138): getCameraInfo: OUT
E/CameraService( 138): onFirstRef::mNumberOfCameras=2
E/CameraService( 138): setCameraFree::E
E/CameraService( 138): setCameraFree::E
E/CameraService( 138): onFirstRef()::doing nothing[/HIGH]

Don't know if that helps you or not.
 
well. as far as redesigning a rom from a different device and having it just boot right up i cant say thats necessarily true, this phone is... quirky

it requires certain binaries, like the init binary in the boot.img ramdisk, and the netd binary if im not mistaken, to be stock or else it wont even boot. and youll want to make sure the partition tables match up correctly. not saying you have to find a phone with matching partitions, just saying you have to check the ramdisk and what not to make sure you adjust accordingly
 
junkie2100 said:
well. as far as redesigning a rom from a different device and having it just boot right up i cant say thats necessarily true, this phone is... quirky

it requires certain binaries, like the init binary in the boot.img ramdisk, and the netd binary if im not mistaken, to be stock or else it wont even boot. and youll want to make sure the partition tables match up correctly. not saying you have to find a phone with matching partitions, just saying you have to check the ramdisk and what not to make sure you adjust accordingly
Click to expand...

I should take a moment to thank you personally because I used your u root/stock 09 root method last night and it worked.I also was running 10.1 with no problems (besides the already known issues). I've never had a rom not work here. You , shin, boricuakiller and others I am surely forgetting inspire me to learn how to give back my time and learn how to develop.
I am still a noob it took me forever to set up adb a while ago
my first os experience outside of indows was my HTC evo way back in 2010. but I've gotten down the google Q&A fairly well so I can only get more capable as time goes on. I read in another topic you said you just started dev work in earnest when you got your sequent, junkie? Hopefully if I keep learning more steadily I will be somewhere more readily available to give back in a matter of months but there is just so much information for somebody who blindly stumbled into the wild world of android. This forum is a goldmine for me though. Someday when I am more financially secure I plan to donate and someday likely sooner than that I plan to go back and hit the thanks button on lots of posts here... when my data isn't throttled lol. So thanks again you guys. And feel free to ignore these noob questions. I try to read through every topic and generally can google answers to questions but I am still ignorant when it comes to... well for example I have to google "android what does [asop msl deodex akop]". Anyway bringing it back home, take for example this topic :
http://forum.xda-developers.com/showthread.php?t=1574401

Could I not reflash 10.1 and use the xposed method to lol idk modify the cm10.1 with jelly bean 4.2.2 (since as first reply said the mini uses MS8655) and the quirks be ironed out via the xposed tool?:

http://forum.xda-developers.com/showthread.php?t=2032900

Apparently wifi works for it and I am such a noob I would love it if the solution was as simple as mixing and matching the right components of cm10.1 for the sequent and for the mini. No really though I googled guides for porting roms and even the most straightforward faqs are like straightforward through a thick jungle . :stupid:

I also only have limited access to my laptop for the time being which slows down my own learning... so maybe if somebody gets bored enough to shed some light on why my theory for just porting and throwing stuff at a wall to see what sticks until the phone codes itself is not feasible. Not really sure how else I can help when there are so many pieces to every piece of the dev puzzle (wish I had chosen CS as my major rather than philosophy derp)
 
well, first thing is first, you got cm 10.1 running??? we were never able to get 10.1 running. make sure you make not of what things you switched out because we will need all the data we can get. that is quite amazing news my friend

are you sure you arent confusing 10.1 with 10? because to my knowledge 10.1 remained unbootable

and yea i did just start back in december trying to figure all this out, got the sequent and i needed a recovery, i break stuff constantly so i had no other option lol. it is a jungle out there but ive spent alot of years navigating the jungle that is google so ive gotten pretty good at picking things out

basically though if you look at the cwm development thread where superr and i did all our tinkering it was just a trial and error kinda thing, we went through and compared a bunch of stuff, compared other devices, looked around to see what we thought looked like it was related to whatever issues we were having, and just kinda went for it. if ya just keep firing eventually chances are youll hit something lol

but yea if you can tell us what you did to get cm10.1 up and running so we can recreate it you will have already contributed a great amount to our cause. and also you can check into getting bluetooth working but that would probably take some tinkering with the kernel though using the android kitchen, modify the init.warp2.rc brcm_patchram service to match the one in the kernel for the mini and see what you come up with. that is if you feel like diving in head first. also check into the camera if possible, their methods might work for us. it might just be that easy you never know. however unlikely a possibility may be it doesnt mean its not worth trying
 
you would actually want to look for msm7630 instead of msm8655. All msm8655 is a tweaked msm7630 and cm uses msm7x30 to build for msms8655. ;)
 
yea, basically anything between the 7630 and 8655 should be basically the same at its core. 8660 is where the real changes happened. what will get bluetooth working though is things using the same broadcom 4330 chipset, possibly the 4329 from what ive read, they are quite similar. and i forget exactly what hardware the cameras were but that can be figured out by looking through the kernel source
 
You must log in or register to reply here.
Back
Top Bottom