Great success!
Atleast partly, I haven't actually flashed anything. So far I've played around a bit with Goro_kn's (sp?) splboot.ko and it appears to be working just fine. So does softbooting boot.img from the modded cyanogen build.
After that I kinda wussed out, I'd rather wait and see if anyone manages to flash the boot.img and get that working before I go any further.
But great work, seeing fastboot working totally MMD.
ddewbofh said:
Great success!
Atleast partly, I haven't actually flashed anything. So far I've played around a bit with Goro_kn's (sp?) splboot.ko and it appears to be working just fine. So does softbooting boot.img from the modded cyanogen build.
After that I kinda wussed out, I'd rather wait and see if anyone manages to flash the boot.img and get that working before I go any further.
But great work, seeing fastboot working totally MMD.
Click to expand...
Click to collapse
How did you do it? The boot.img comes up as an incorrect size for me.
HunteronX said:
How did you do it? The boot.img comes up as an incorrect size for me.
Click to expand...
Click to collapse
Yeah, it looks like I got a little ahead of myself. I tried the classic "fastboot boot boot.img" and it appeared to be uploading the image but it just hung there.
And poking around my old memory banks I remembered the old syntax. Booting with "fastboot boot kernel ramdisk_recovery.img" yields the same result.
It's been way too long since I last messed around with fastboot.
ddewbofh said:
And poking around my old memory banks I remembered the old syntax. Booting with "fastboot boot kernel ramdisk_recovery.img" yields the same result.
It's been way too long since I last messed around with fastboot.
Click to expand...
Click to collapse
Did you manage to boot into CyanogenMod at all, using goroh_kun's method?
I know what you mean about fastboot though... I have used it for ages, since I gave my T-Mobile Pulse to my little brother.
HunteronX said:
Did you manage to boot into CyanogenMod at all, using goroh_kun's method?
Click to expand...
Click to collapse
Not yet, but I'll keep trying.
ddewbofh said:
Not yet, but I'll keep trying.
Click to expand...
Click to collapse
What could we do to solve this?
I think it involves some more editing of the custom SPL (which I don't have a clue how to do ) and/or checking, then rebuilding the boot.img to make it the correct size for fastboot...
HunteronX said:
What could we do to solve this?
I think it involves some more editing of the custom SPL (which I don't have a clue how to do ) and/or checking, then rebuilding the boot.img to make it the correct size for fastboot...
Click to expand...
Click to collapse
I'm thinking I should hold off on trying a little more seeing how the real devs are obviously booting this. I'm guessing I'm just missing something somewhere and it's a nightmare to navigate the threads here.
ddewbofh said:
I'm thinking I should hold off on trying a little more seeing how the real devs are obviously booting this. I'm guessing I'm just missing something somewhere and it's a nightmare to navigate the threads here.
Click to expand...
Click to collapse
That's what I think too...
Also, thanks for the info, ddewbofh.
This is excellent news.
Just to double check CM6 = Android 2.2?
sorry ... but anyone can explain in plain english ? can we flash CM ? on x10 ?
No
10chars.
AndyD777 said:
Just to double check CM6 = Android 2.2?
Click to expand...
Click to collapse
Yes it is.
instigator008 said:
Yes it is.
Click to expand...
Click to collapse
In a Mr Burns style voice "Excellllleeeennnt"
AndyD777 said:
In a Mr Burns style voice "Excellllleeeennnt"
Click to expand...
Click to collapse
Eeeeeegsalad
Hold your horses guys....well be quite a while before we have a fully useful 2.2 cm6 as in addition to the bootloader they also have to get drivers working for x10 hardware. What good is cm6 if the camera, wireless and calling doesn't work?
Give them time to nut it all out.
MeZmeriZe_ said:
Hold your horses guys....well be quite a while before we have a fully useful 2.2 cm6 as in addition to the bootloader they also have to get drivers working for x10 hardware. What good is cm6 if the camera, wireless and calling doesn't work?
Give them time to nut it all out.
Click to expand...
Click to collapse
Naturally, but it's still nice progress. And the fact that the X10 shares large portions of it's platform with the HTC Desire is bound to help. Since both have use Snapdragon they share the same GPS, cellular modem, audio, network, cpu, graphics etc. Looking at the spec sheets from Qualcomm they're essentially the same device but with different shells, cameras and screens since the Snapdragon kit does everything.
cannot wait to get the benchmark result of Xperia X10 running Android 2+. I'm hoping X10 can get somewhere around Nexus One benchmark.
I have never thought about that, if they do have the same components, the drivers should be the same for each shared component?
Haha its kind of funny how the only differentiating factor is screen, shell, and camera!
Most likely they don't have the same hardware.
Sound, camera, display are 100% different.
RF chip might be different too and in this case drivers are needed for wifi, gps, bluetooth, 3g.
The best part, the drivers are most likely available in the kernel sources released by SE and they only have to be ported to the newer kernel.
Sometime changes in the code is needed, some time only copy the driver from a tree to the other is enough.
Related
Thanks for stopping to read this.
I wanted to know if this has been rooted yet, and also if I can load it up to honeycomb yet?
On a side note does anyone know if the snes and other emulators work well on it?
RiffyDivine said:
Thanks for stopping to read this.
I wanted to know if this has been rooted yet, and also if I can load it up to honeycomb yet?
On a side note does anyone know if the snes and other emulators work well on it?
Click to expand...
Click to collapse
Hello,
Replacing with the firmware makes the device root. You have multiple to choose from. TNT lite. Vegan Etc..
I have not seen honeycomb firmware yet but the word is that the devs are looking in to in and will be available once it is fully tested.
I have seen the emulators work on the viewsonic so the question to that is YES..
Enjoy..
I think most of us bought this for the hardware knowing that Android developers will eventually bring us everything we want and more. If the tab can't do "it" now I am sure it will soon.
cd112 said:
Hello,
Replacing with the firmware makes the device root. You have multiple to choose from. TNT lite. Vegan Etc..
I have not seen honeycomb firmware yet but the word is that the devs are looking in to in and will be available once it is fully tested.
I have seen the emulators work on the viewsonic so the question to that is YES..
Enjoy..
Click to expand...
Click to collapse
Thanks, it will be here tomorrow. I just needed to find the specs sheet on tiger and was sold. Can't believe it's a 150 dollars off right now, it's less then my cellphone was. Glad it is on sale, it can replace the crappy dual boot viewsonic tablet I got. Wish it had said on the site hey this isn't real android on here.
I was also reading, people say flashing a CFW is simple with the gtablet. Something about how there are no blocks or anything in the way to keep you from doing it which is great. So I will just look around in here for the how to flash unless it's as simple as CWM.
Yep, just CWM! Though, possibly a touch more than normal with a simple phone, like the Droid. You need to repartition it in CWM for best results, then wipe everything, then install the ROM. Depending on the ROM, you most likely will want to install GAPPS after. That's pretty much it! Most of the ROMs come with decent kernels, I've noticed.
Good thread to step through the process.
www.forum.xda-developers.com/showthread.php?t=1016695
chadness said:
Yep, just CWM! Though, possibly a touch more than normal with a simple phone, like the Droid. You need to repartition it in CWM for best results, then wipe everything, then install the ROM. Depending on the ROM, you most likely will want to install GAPPS after. That's pretty much it! Most of the ROMs come with decent kernels, I've noticed.
Click to expand...
Click to collapse
What is gapps? Is it a stock apps store just for the gtab.
RiffyDivine said:
Wish it had said on the site hey this isn't real android on here.
Click to expand...
Click to collapse
It is real android, they just their own "layer" on top of it. It is fairly easy to install another Rom on this thing, just make sure you read, understand, and follow the directions carefully.
Once you get it installed, unless you feel comfortable with possibly having to do a bit of work if you "mess it up", I would try not to fool around with it too much. I've installed Vegan-Tab 5.1.1, and a kernel, and it runs fine, so I try to just use it as is...
back it up with nvflash before you start rooting....that will prevent you from bricking your tab. I just got mine last week and its amazing how well it works . I am currently testing our different roms on it to see which one I like the best. Vegan 5.1.1 and TNT Lite 4.4 are pretty nice to start off with.
TheKaz said:
It is real android, they just their own "layer" on top of it. It is fairly easy to install another Rom on this thing, just make sure you read, understand, and follow the directions carefully.
Once you get it installed, unless you feel comfortable with possibly having to do a bit of work if you "mess it up", I would try not to fool around with it too much. I've installed Vegan-Tab 5.1.1, and a kernel, and it runs fine, so I try to just use it as is...
Click to expand...
Click to collapse
No no sorry, I ment the other viewsonic tablet. The one that dual boots win7 and x86 android.
rbansal2 said:
back it up with nvflash before you start rooting....that will prevent you from bricking your tab. I just got mine last week and its amazing how well it works . I am currently testing our different roms on it to see which one I like the best. Vegan 5.1.1 and TNT Lite 4.4 are pretty nice to start off with.
Click to expand...
Click to collapse
Always good to backup, I assume as long as you get that even if you totally mess up you can just reflash it and try again. It will be here tomorrow around 11ish, so once I get done at the office going to get a few ciders and attack this thing.
RiffyDivine said:
What is gapps? Is it a stock apps store just for the gtab.
Click to expand...
Click to collapse
Depending on the package, it will be some of the missing Google stock apps. such as the Market.
One other thing - boot it and set up wireless so you can get any over the air updates before you put a new ROM on.
chadness said:
Depending on the package, it will be some of the missing Google stock apps. such as the Market.
One other thing - boot it and set up wireless so you can get any over the air updates before you put a new ROM on.
Click to expand...
Click to collapse
Thanks mate, I planned to try out the stock first just to see what they did with it.
Oh, one other thing. How is the screen on this? Nice and clear? I only ask cause on the viewpad 10 I bought some months back, well the screen looks awful unless you got it maxed brightness, it just always looks like there is dust on it.
RiffyDivine said:
Oh, one other thing. How is the screen on this? Nice and clear? I only ask cause on the viewpad 10 I bought some months back, well the screen looks awful unless you got it maxed brightness, it just always looks like there is dust on it.
Click to expand...
Click to collapse
I think it looks really good, as long as you are at the right angle. You probably heard that it has a narrow field of view if you tilt it up or down (while being held in landscape). But, when looking at a decent angle (tilted less than 45 degrees, maybe?) the screen itself is bright and clear.
chadness said:
I think it looks really good, as long as you are at the right angle. You probably heard that it has a narrow field of view if you tilt it up or down (while being held in landscape). But, when looking at a decent angle (tilted less than 45 degrees, maybe?) the screen itself is bright and clear.
Click to expand...
Click to collapse
That sounds about the same for the angles as the viewpad 10. My only problem was that it honestly always looks like a dusty. But I will know for sure in about 3 hours when I am done here. Don't most tablets have issues if you try to tilt them too much one way or another?
cdavisccs28 said:
Good thread to step through the process.
www.forum.xda-developers.com/showthread.php?t=1016695
Click to expand...
Click to collapse
weird seems that link doesn't work.
EVEN WORSE, there is like 2 pixles that are red. Are they dead or just somehow locked?
CyanogenMod 7 (w/ Gingerbread 2.3.4) for Vibrant
Not supported anymore due to issues with dialing 911. We strongly suggest that Vibrant users of CM7 save their data and install a Samsung ROM and restore data to it
Save this post
Since this obviously replaced the previous CM information. There is still no gps support, correct? I know it was stated in all of the old info, but I didn't see any mention of it in the new logs. I just wanted to confirm prior to going ahead with the installation.
zyrinx said:
Since this obviously replaced the previous CM information. There is still no gps support, correct? I know it was stated in all of the old info, but I didn't see any mention of it in the new logs. I just wanted to confirm prior to going ahead with the installation.
Click to expand...
Click to collapse
http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=95
Excellent. Thanks. A simple "No" would have sufficed, but I do appreciate the link to current issues.
Does this mean that this CM7 is from the OFFICIAL CM people and not the things that our devs here made?
xriderx66 said:
Does this mean that this CM7 is from the OFFICIAL CM people and not the things that our devs here made?
Click to expand...
Click to collapse
Official CM will be made from what we build here. There is not "Official people" as such - teamhacksung are the ones doing the SGS specific stuff for CM.
anyone else having issues flashing todays update? I flashed it now my phone will not boot.
Indeed. There were several posts in the development thread about it causing boot issues. It's only with the Vibrant though. They suggested flashing a new kernel/old kernel and that should fix it.
zyrinx said:
Indeed. There were several posts in the development thread about it causing boot issues. It's only with the Vibrant though. They suggested flashing a new kernel/old kernel and that should fix it.
Click to expand...
Click to collapse
Sorry - that is only to go back to previous. We will be uploading another soon if we've fixed what we think we just fixed. But to get your phone back, just flash an older kernel, and then flash 5/1 update and you should be on CM7 again, ready for new update which will happen soon I hope.
Awesome. Looking forward to it.
I know these numbers are irrelevant, but what kind of quadrant numbers is this running at?
Curious as to the lack of GPS functionality, is it because of a lack of open source drivers?
And if it is, then why do other GalaxyS devices have working GPS when (i dont think) they dont have any more new open source files then us?
karimsaud21 said:
Curious as to the lack of GPS functionality, is it because of a lack of open source drivers?
And if it is, then why do other GalaxyS devices have working GPS when (i dont think) they dont have any more new open source files then us?
Click to expand...
Click to collapse
Different GPS chip on Vibrant.
Amazing thread.
Everyone should know he also does not have a Vibrant and works mostly on the Captivate. The fact he is aiding us, speaks volumes. I hope you all appreciate his extra efforts.
I tried to make an install guide (signature). Its not perfect, but it may help (differences from the video)?
I totally agree s15274n . Btw cm7 rocks
Sent from my SGH-T959 using XDA Premium App
Quick question, does the latest build charge while powered off? Don't want to flash to find out.
Sdobron said:
Quick question, does the latest build charge while powered off? Don't want to flash to find out.
Click to expand...
Click to collapse
No, it will turn on. Tho why it matters I never understood. We will support low power mode someday I'm sure, but very low priority. Just turn the screen off, use quiet hours ...
Thank you for posting this. I have a quick question though. I lost my USB driver cable to my vibrant (I charge it via a plugin charger now.) Is there any possibility that I can install CM7 via the Marketplace (from Clockwork Mod or the another automatic install app) without going through all these steps?
I will be coming from Nero....
Thanks for all your hard work!
Quick question I flashed cm7 yesterday and have been amazed by everything except one thing. The color levels specifically the blacks are horrid. I can't use any wallpaper that has shades of blacks or it just looks very low quality. Is this a voodoo thing?
Sent from my SGH-T959 using XDA App
And boom goes the dynamite!
reverendkjr said:
And boom goes the dynamite!
Click to expand...
Click to collapse
Thanks rev, great work as always!
I'm really liking this! I know this is going to sound strange, but did we lose the capability to "Reboot" and reboot into recovery and webOS? And Screenshot?
a40dayflud818 said:
I'm really liking this! I know this is going to sound strange, but did we lose the capability to "Reboot" and reboot into recovery and webOS? And Screenshot?
Click to expand...
Click to collapse
It needs to be added into the power menu it's not stock from google like that
a40dayflud818 said:
I'm really liking this! I know this is going to sound strange, but did we lose the capability to "Reboot" and reboot into recovery and webOS? And Screenshot?
Click to expand...
Click to collapse
Screen shot is power and volume up or down, can't remember which one
Sent from my PG06100 using Tapatalk
Thanks again. Couldn't resist upgrading and holy hell was it worth it. Love the cmteam.
Sent from my cm_tenderloin using xda premium
It's funny... I didn't realize that my power menu was different until I read the responses to this thread.
Like I said in IRC: nice work Rev )
These vids are so handy to play on your screen while you update the TP, it gives you a good feeling like: ohhh right and ahhh how did I forget that cmd line etc
good backup, good initiative
I know several people have said the same thing about my videos. Sometimes, it's just nice to see someone else do it first, even though you are more than capable of figuring it out yourself.
reverendkjr said:
I know several people have said the same thing about my videos. Sometimes, it's just nice to see someone else do it first, even though you are more than capable of figuring it out yourself.
Click to expand...
Click to collapse
Thanks for u'r Tut'z.... I started to check u'r YT channel daily for updates... Although I've already seen all your vidz a couple of times... IG v2.0 & CM9 will be playing and guiding me step by step when ever I decide to mod my TP... Maybe this weekend....
I do have a ? regarding Dual Boot and more specifically Triple boot... Which u seem to have been successful with... Your CM9 vid lists WebOS/ICS/CyanogenMod on MoBoot....
Related to the :
CAN I MAKE A TRI-BOOT SYSTEM? (WebOS, CM7, and CM9)
Yes, but don’t bother. There may be instructions forthcoming on this, but it’s a bit advanced - just pick one.
Click to expand...
Click to collapse
over at RootzWiki...
Can I PM u the ? .... Don't want to thread-jack more then I've already....
Posted the ? or ideas on this thread: [Q] Triple boot idea (WebOS,CM7.1,CM9)
Y314K said:
Thanks for u'r Tut'z.... I started to check u'r YT channel daily for updates... Although I've already seen all your vidz a couple of times... IG v2.0 & CM9 will be playing and guiding me step by step when ever I decide to mod my TP... Maybe this weekend....
I do have a ? regarding Dual Boot and more specifically Triple boot... Which u seem to have been successful with... Your CM9 vid lists WebOS/ICS/CyanogenMod on MoBoot....
Related to the : over at RootzWiki...
Can I PM u the ? .... Don't want to thread-jack more then I've already....
Posted the ? or ideas on this thread: [Q] Triple boot idea (WebOS,CM7.1,CM9)
Click to expand...
Click to collapse
I am NOT tri-booting. The ICS that you saw was Evervolv and it was broken. I removed it right after making that video. I will NOT EVER be booting two different versions of Android on the same device.....EVER.
A grateful thank you.
Rev, I would like to thank you for your great tutorials. I watched your cm for dummies several times before I got the nerve up to possibly brick my new TP. Needless to say I didn't! I am running Xron 2.9.1 and plan to flash ICS once its a little more mature. I watched your video on flashing Xron and fixing the prop.build and both helped tremendously. So thank you.
reverendkjr said:
I am NOT tri-booting. The ICS that you saw was Evervolv and it was broken. I removed it right after making that video. I will NOT EVER be booting two different versions of Android on the same device.....EVER.
Click to expand...
Click to collapse
I am awaiting your ICS vs. CM7 review, but since you made the X-Ron video you've seem to have gone to CM7... and now ICS (which that I do understand).
Was the xron before cm 3.5? Just curious, I had avoided the alpha till I found your You-Tube and phtt, so straight forward that I did it and no turning back, plus I now understand more of the root terminology. Dual boot's just a plus.
Soon Root my HTC Ineradicable S HBOOT 1.13.0000, now that I have the basic understanding.
texastutt said:
I am awaiting your ICS vs. CM7 review, but since you made the X-Ron video you've seem to have gone to CM7... and now ICS (which that I do understand).
Was the xron before cm 3.5? Just curious, I had avoided the alpha till I found your You-Tube and phtt, so straight forward that I did it and no turning back, plus I now understand more of the root terminology. Dual boot's just a plus.
Soon Root my HTC Ineradicable S HBOOT 1.13.0000, now that I have the basic understanding.
Click to expand...
Click to collapse
I am working on the comparison video this weekend. I'm hoping to get something up tomorrow. There is just so many things to compare that I'm trying to make it worth watching. Check tomorrow evening for it.
Thanks Rev
Let me add my thanks for the great vids. WebOs was fun, but ICS is the tablet experience I was looking for when I bought the TP.
Just an FYI for those of you who, like me, hadn't installed CM7 in a while and got stuck on the command line screen with a device not found message and couldn't figure out what to do next.
Reboot your touchpad into WebOS. Select device info, reset options, then reset (or maybe it's reboot--can't remember). When the screen goes black, hold the volume up button and the device will reboot into a screen with the USB symbol. Now enter the command
novacom.exe boot mem:// < ACMEInstaller2
in the DOS window on your PC and you should be all set (assuming you have the necessary files in the appropriate directories as described by reverendkjr).
When I installed cm9 I felt that same feeling I had when first installing android. But this time having rev's video was a good feeling to be able to follow all the correct steps. Thanks rev
Newbie here.
And thanks a bunch for this!
I did everything as per the instructions and it worked great.
However i left the device idling and it wouldn't wake up in the morning! I can however see the blinking light on the home button. Any advice?
Like I said, newbie here.
msnarain said:
Newbie here.
And thanks a bunch for this!
I did everything as per the instructions and it worked great.
However i left the device idling and it wouldn't wake up in the morning! I can however see the blinking light on the home button. Any advice?
Like I said, newbie here.
Click to expand...
Click to collapse
Hold the Home+power button for a few seconds it will wake up
Good Job.
Thx
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
I wanna know too...
bump.
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
HMZX said:
I wanna know too...
bump.
Click to expand...
Click to collapse
I think you can definitely test w/o causing permanent damage. For the smoothest test experience, you'll want to be familar with a custom recovery and the backup/restore modes available along with the type of internal memory unlock used on the device (Revolutionary or HTC official method).
Once you're familar with the basics, it would be fairly simple to test. The combinations for testing, off the top of my head, would be:
1) Sensation kernel and EVO 3D ROM.
2) Sensation kernel and Sensation ROM.
3) EVO 3D kernel and Sensation ROM.
Speaking from experience, once you're familar with how to load kernels and ROMs, the process is fairly generic across devices once write access to the internal memory is obtained.
Again, I'll re-iterate the importance of making a proper backup and being familar with the restoration process.
There are only two main hazards which come to mind:
1) Make sure NOT to flash the radio, bootloader, or any other file. ONLY flash kernel/system partitions.
2) Before flashing kernel/system partitions ensure the partition sizes between devices are the same, or EVO 3D is larger. Not sure the device limits and stops partitions from overwriting each other as I know some older devices did not and this caused an unrecoverable damage.
I'm sure if I missed anything, somebody else will post up. Hope that helps provide some technical background and logic to the approach! Keep us updated!
Thanks for the reply. I'm already familiar with flashing kernels/roms and how to make a nandroid backup etc so that isn't a problem. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Yeah I have a GSM phone so that's why I said GSM. Also wouldn't porting to the GSM version be easier then to the CDMA version since the sensation is also GSM?
Anyways I'm kinda busy today but I will try to see if it boots on my phone tomorrow and post my results. I'll.also try to get the camera to work by copying libs like you suggested.
Sent from my HTC EVO 3D X515m using XDA App
vipirius said:
Thanks for the reply. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Click to expand...
Click to collapse
Answer to first question: partition sizes are generally mentioned in a handful of different locations depending on the device: /proc/partition(s), /proc/emmc or /proc/mtd off the top of my head. Since the devices are similar and others have already tried this approach, probably not a concern, but none the less never hurts to learn more!
Answer to second question: the cameras (2 of them for 3D) on this device, along with the 3D display are the two biggest difficulties in porting AOSP such as CM to this device, in my opinion. they use closed source proprietary code from HTC. this requires a bit of reverse engineering and kanging from other random sources in order to get a final working product. personally, i wouldnt invest the time/effort into it, but others might find it a beneficial endeavor for themselves. either way, you're guaranteed to learn a bit about cameras! as stated above, all android libraries are loaded in /system/lib.
For the camera, I view android as having essentially three components contributing to a fully functional camera.
1) Camera drivers in the kernel
2) Camera libraries in /system/lib
3) Camera application apk file for Android UI
These three need to work together to at least some degree in order for there to be some functionality in the camera.
Gumby63 said:
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
Click to expand...
Click to collapse
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
joeykrim said:
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
Click to expand...
Click to collapse
Well yeah it completely reboots back to the splash screen. During the bootanimation, I can't get a logcat and adb says there is no device connected. This isn't my first port but I've never had this happen lol. I'll look into what you said.
Sent from my HTC Flyer P510e using Tapatalk
Well, I successfully installed Android Revoltion HD 3.6.13, It boots, everything seems to work, however I didn't test GPS and BT yet. And the camera is well, half working I guess. The camera app opens, and i can see the controls etc but no image comes, and when I press the capture button the flash pops but the app FC's after that. I'm gonna try flashing [MOD] Camera from HTC Amaze 4G, v0.11 and see if it works. If it doesn't I'll copy over all the camera related libs I can find from my old ROM and see if it works then.
Edit: Hahahaha yessss it works I just flashed the Amaze camera app and now camera works only 2D of course but it's enough for me. I'll keep testing for a few days and of there aren't any serious bugs I can find I'll be using this as my daily driver from now on
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
vipirius said:
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
Click to expand...
Click to collapse
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
t3project said:
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
Click to expand...
Click to collapse
Yeah that's what I was going to do, but thanks anyways. I'll report back on my success.
Gumby63 said:
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Click to expand...
Click to collapse
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
im not sure what you read but IT WAS WRONG..........
while you can do some of this stuff from your phone, you can not do a complete port properly without a computer
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Gumby63 said:
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
vipirius said:
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
Click to expand...
Click to collapse
this is only patrialy the problem. flashing roms doesnt affect the radio so that wouldnt change but i there are some other libs that need to be moved that are associated with communication to the radio. cant remember which off the top of my head
Gumby63 said:
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Yeah I thought the article I read was Bull****! I wish I could remember where I read it to show you guys what it said but just can't remember for ****... Lol!
Well Thanks for Confirming guys...
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
danial.aw said:
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
Click to expand...
Click to collapse
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Ya I did message him... Unfortunately I believe he is busy
[r.]GimP said:
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Click to expand...
Click to collapse
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
SnowLeopardJB said:
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
Click to expand...
Click to collapse
Stuff like this keeps schooling me every day, brain starting to hurt
That being said, I setup an Ubuntu environment earlier today, from one of the guides in chef central, using 12.04 64bit, got all the packages, but i'm terrified to sync a potential 10 gigs of stuff, what exactly should i be syncing to on github for our device, and say for illusion rom to try building from source?
and as I side project today, I nearly got a zte x500 to take a custom rom and recovery from the stock recovery, after noticing ZTE signed their packages with the test keys, just needed to figure out the mmcblk for recovery for the cricket score <edit> I know the syntax that particular updater script needs now, but dont have access to the phone til monday. the person is getting a new phone anyway but it's my pet project to flash a custom rom and recovery from the stock recovery and good practice doing updater-scripts from scratch </edit>
Been a fun day.
danial.aw said:
Ya I did message him... Unfortunately I believe he is busy
Click to expand...
Click to collapse
I am not "busy" haha, just on vacation without my computer out of country
Ahh well hope you have fun and get back to your computer soon times lol
Hey Morris any chance you are back and kicking?
morrislee said:
I am not "busy" haha, just on vacation without my computer out of country
Click to expand...
Click to collapse
Just checking, would it be possible for you to make an inversion patch for your hybrid modem?