Database Develop

Cyanogen Mod Offically Supports the IS! - No Download yet, still in beta

UPDATE: 2 Cyanogen developers have picked up the Incredible S and it is being officially supported!! The ROM is in Beta and will be released when ready.
Remeber, the first rule of cyanogen: Don't ask for deadlines!!​
Click to expand...
Click to collapse
Previous version of this post, kept for historical reasons:
Code:
I am sure everyone here wants to see CM7 hit this device. I am also sure that in our collective efforts, we can do it. At the moment, it is just me (or no one else is saying they are trying ;)) I basically want to try and get a team of people to crack the porting problem, because so far I am unable to do it on my own.
Finding information is proving difficult, and I just keep hitting dead ends. Is anyone willing to help? Has anyone ported a ROM from one device to another before? Can anyone point me towards information on how to start / debug?
As a community, this will get done a lot quicker, so if anyone can help please post here. If you idea of helping is posting "[I]I can help, what can I do / tell me what to do /give me something to do[/I]" then thanks, but no thanks.
[SIZE=3][B]Please keep this thread clear of chatter so it can be used for discussing the problem at hand.[/B][/SIZE]

I have ported from the HTC Dream to the HTC Diamond ...
If you wish to get started the way i do it ... Take a cm build from the closest device ... Say the DHD ... And chuck the system.img into an official update zip or any other zip with a working boot.img etc ... Then try booting directly ... If it bootloops ... The first thing you should try is to replace /lib from a stock rom ...
This will get you to boot surely ... But if you manage to boot directly then keep the libs ... After that we need the appropriate libs extra things like the secondary cam that u can take from the stock rom ...
A more detailed way to do it would be to get the ported libs working by using logcat to see whats wrong and replace only the related libs from a stock rom ... Keeping stock libs will make performace related things such as battery in the same state as stock ... So it is best to keep the ported libs ...
I would have done this myself by now but i have a s-on devoce :-/
Anyway can you tell me whats wrong with your attempts? Where do you get stuck? Which device are u trying to port from?
EDIT: idon see why you hit dead ends if u port from a similar device it should be no problem to boot ... Heck ports from the dream to the bloody winmo diamond worked out of the box ... The dream libs worked fine ... Would be nice if u could chuck us a logcat ... Even if i cant figure it out ill ask neopeek ...hes a pro but idon think this will go that far
Sent from my HTC Incredible S using XDA App

I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25
I will try what you said, it's a good starting point, thanks!
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...

Hehe ... Good point ... U cant get a bootloop if u dont even start boot ... I admit ... U sure have a funky way of trying things out ...
EDIT: that logcat ... Did u get it with what i said or what u tried?
Sent from my HTC Incredible S using XDA App

Both gave me that result. Can't really find out what it means other than it couldn't mount the system partition, no idea why
Sent from my HTC Incredible S using Tapatalk

I think the problem comes earlier ... Look at what you have said ... That failed to format part ... I think it screwed up halfway and now its empty ... Have you compared the update script with the one from the dhd? You are porting from the dhd right? Its the best option ...
Sent from my HTC Incredible S using XDA App

I use the same script I use for lpremix so I know the script is fine. Which is why I am stuck.
Sent from my HTC Incredible S using Tapatalk

Hmmm ... We need to narrow this down ... Try copiying in only /app /framework /media ... And also try using the older setup with the stock build.prop ... If u can boot this then the problem is in the rest ...
EDIT: did u also try different update scripts? Try using the dhd one as it is ... I think the problem is there might be a difference in the way the IS is partitioned compared to the dhd ... Cuz idon think we really have a mmc's upto 25
Sent from my HTC Incredible S using XDA App

Have you tried converting the Ace updater script to update script then changing the mount partitions to say from:
Code:
format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");
to
Code:
format SYSTEM:
format CACHE:
format BOOT:
Then convert back?

K bro i think ive got some thing ... In /system/etc there is a file called vold.fstab ... Please do a comparison ... There might be a difference there ... Check the cm one with stock ... Also compare the cm7 update script from ace and the update script from a lp remix ... Maybe you just need to change the partition name ... Also try removing those lines completely from the script you are using ... Chuck all the lines related to format...
EDIT: its getting a little late ... Its around 330 am now ... I think ill go to sleep ... Ill see if i can think up of anything else for u bro ... Gnite every1 -_-
Sent from my HTC Incredible S using XDA App

looks like u have the same prob as me bro

l0st.prophet said:
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25...
Click to expand...
Click to collapse
As far as i know Desire HD is ext3 and IS/DS are ext4.
Try to change the partition information.
See my previous post.
l0st.prophet said:
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
Click to expand...
Click to collapse
Also here in your script you have a reference to /system/bin/sh which is probably missing from your rom.

hmm didnt even read that, but yes it shud be 4 o.0 or is that why my script is fkin me up?
imma test 3 anyway...

Im back from bed ... Maybe marylandcookie is right ... But where can that problem be? He is using the lpremix update script that usually works not the dhd script ... So why is it trying to chuck up ext3? Are u sure we are ext4?
@marylandcookie: do you have a nickname ... Ur name is real handfull to type out -_-
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Sent from my HTC Incredible S using XDA App

Ext3 works fine, but I will try ext4 anyway. It's us more likely to be a problem in the system files so I will check void.fstab file
The sh file is there, the system partition just isn't mounts properly
Sent from my HTC Incredible S using Tapatalk

it's too diffcult for me...but i believe we can

knightrocker said:
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Click to expand...
Click to collapse
I'm not sure what you mean, I suggest you look at the partition table. It's differant from mtd blocks cause its nand, system is definately mmcblk025
Sent from my HTC Incredible S using Tapatalk

Really? Still not used to this whole nand partition thing
Much better with android itself have made any progress?
Sent from my HTC Incredible S using XDA App

I won't today or until Tuesday as I am on holiday and away from a pc, but I will get back to it next week
Sent from my HTC Incredible S using Tapatalk

Ok then ... Ill see if i can think of something by then ...
Sent from my HTC Incredible S using XDA App

[Q] Image modifications.. need help.. :)

Hi experts.. sorry for the totally noob questions..
1) is it possible after i extract any "boot.img" from any kernels built, i can edit those .rc files and then rebuild it?
2) to edit one's cpu properties (freq, voltages n so on) can i just edit .rc files or i need to build from source? If source, which folder/files i need to start?
Thanks.. :[email protected]#$%&*
Sent from my LG-P990 using XDA App

Yep, this is most certainly the right section, namely development. Questions definitely don't belong into the QUESTIONS AND ANSWERS section. But go on.

To make my /system, /data and /cache formatted ext4, just edit "init.tegra.rc", "init.rc" or both? Notice at init.rc, there are line mention yaffs2, then at init.tegra.rc, ext3? Which 1 should i edit?
Sorry guys.. just that i'm a slow learner.. (
Sent from my LG-P990 using XDA App

ghadap said:
To make my /system, /data and /cache formatted ext4, just edit "init.tegra.rc", "init.rc" or both? Notice at init.rc, there are line mention yaffs2, then at init.tegra.rc, ext3? Which 1 should i edit?
Sorry guys.. just that i'm a slow learner.. (
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Hello,
I haven't tried modifying ROMs. But my suggestion would be to get an ext4 ROM and study how its scripts work

Ive tried view all the sources, but i can detect which file/folders i need to edit.. as example, i know to create my own freq, i need to look a file at /driver/freq/freq.c... but which line i need to focus?
Sent from my Cyanogenmod 7.1.0

ghadap said:
Ive tried view all the sources, but i can detect which file/folders i need to edit.. as example, i know to create my own freq, i need to look a file at /driver/freq/freq.c... but which line i need to focus?
Sent from my Cyanogenmod 7.1.0
Click to expand...
Click to collapse
I honestly have no idea. But there are a lot of devs here who have experience with kernel source. Try maintainers from cm7, paul (modaco), spica, or topogigi.

Hopefully they read this thread @ my pm.. like to learn..
Sent from my Cyanogenmod 7.1.0

[Q] [ICS][ROM] roms with IA2SD+ script

Hello,
I'm one of the unlucky who used MeDroidMod and got his mic ****ed with the last update.. following by the blatant disregard for an open source community.
I really like the way IA2SD+ handled things tho, I've looked around but didn't find any other rom using it.
Is there any? Or can experts having used a few scripts like that can enlighten me about other and just as nice scripts to boost the internal memory?
Thanks

I don't know internally how iA2SD but it does seem to mount /sd-ext as /data, which basically all AD2SDX scripts do, so amarullz AD2SDX script should do, even though iA2SD is much better
Sent from my Nexus One using Tapatalk

Yeah the idea of ia2sd is coming from a2sdx but on my second version with ia2sd app I changed all my script for a more optimized one and still the same idea but with the idea of choosing whitch app you want internal or external. Anyway, for now, I didn't really try my script on other version and medroidmod will continue to be updated event if the thread is closed, our Google code always contain the last version and will continue to update over ota too.
For your mic try 1.4.3 with full wipe first and backup before starting.
First time that don't have mic issue too.
New kernel, new drivers on that version

Thanks timbit123, I'll be sure to check it out. I rolled back to 1.4.2 for now - didn't have much time to full wipe yesterday.
I have to say your script really rocks. Other 2SD scripts usually ****ed up my backups, and restores, and I didn't like the fact I didn't know what was going where. If the 1X was released a few months later, I'd keep on using my N1 for a while thanks to you.

Timbit, I really think your ia2sd is a fantastic solution for our aging Nexus Ones.
Is there any chance it can be made available stand alone so that it can be used with any ROM? You could give it its on well deserved thread on XDA Android Dev forum (will it work on any rooted Android phone?)
Anyhow, could make many people happy
Sent from my Nexus One using XDA App

Yeah as long the rom is compatible with init.d it should work without issue. I will probably make it installable from the ia2sd app. Just need some times to make this out and make tests

timbit123 said:
Yeah the idea of ia2sd is coming from a2sdx but on my second version with ia2sd app I changed all my script for a more optimized one and still the same idea but with the idea of choosing whitch app you want internal or external. Anyway, for now, I didn't really try my script on other version and medroidmod will continue to be updated event if the thread is closed, our Google code always contain the last version and will continue to update over ota too.
For your mic try 1.4.3 with full wipe first and backup before starting.
First time that don't have mic issue too.
New kernel, new drivers on that version
Click to expand...
Click to collapse
Regarding the mic issue, it still exists in v1.4.3 even though I did full wipe and format system before flashing the ROM. I had to wipe cache and dalvik-cache after the phone rebooted and that solved the mic issue.

timbit123 said:
Yeah as long the rom is compatible with init.d it should work without issue. I will probably make it installable from the ia2sd app. Just need some times to make this out and make tests
Click to expand...
Click to collapse
please!!!!

ok, i'll build a version sometime next week and start a thread in dev section when i'll release a version. Probably it will be only the script because, application can only run in ics, not compatible with gingerbread. need some times to remake that application

That's great news TimBit. Merci!
Sent from my Nexus One using XDA App

[DEV][ICS+SENSE][Mar.20.2012]HTC One V development[Source+RUU]

Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download

Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.

I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595

PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..

Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot

When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.

Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v

Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^

PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?

orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★

PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!

I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium

2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.

Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5

I'll upload the ROM port I just made a few days back. It has most of what I thought might work..

Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.

I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..

Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5

Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.

I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!

[DEV][WIP]Incredible Sense 3.6[No Boot][Apr.13.2013]

Here is my port thus far:
X Disclaimor - Rom does not boot meaning this is not working yet X
I think since sense 4 was obtainable I'd like to think Sense 3.6 is too.
Now, i'd like to ask for a little help if anyone is available.
Plus, I know developers because I am one; we have an insatiable palette for a good project.
I've discovered two things that have made me feel like i'm stuck:
4/12/2013
1) I am not sure what else I can remove from the system dir to decrease the size to what is needed ~ 272524902.4 bytes (259.9Mb)
The Roms system dir is ~274083573.9bytes (261.4Mb); I basically need to know what else I can get rid of that equal up to 1558671.5 bytes (1.5Mb)
Here's the catch- I already took out the weather from media and apps and have symlinked them from the data partition.
2) I am not sure if I have correctly made the kernel.
I have a boot.img from the sense 3.6 rom i used to port. And I added the bootclasspath from the base kernel.
I also have renamed the proper files that needed to be renamed with inc.
Update: 4/13/2013
I've shrunk the system/usr dir down and now the port is under the size limit.
I have also tinkered with the boot.img more. Can someone check it to make sure that I have done is okay..
`Link in my sig:

First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So far I've symlinked system/media/weather to data/system.weather and the system/app dir to data/system.app.
This is what i'm using:
symlink("/data/system.app", "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.app");
symlink("/data/system.weather", "/system/media/weather");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.weather");​
Do you think i could do the same with the system/vendor dir?
Edit: Don't need to worry now that the current port's system partition,which is now uploading, will be under the size limit.

*Bumpdated*
v1_1 Upload

Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible

We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.

ChemicalSymphony said:
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
Click to expand...
Click to collapse
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
tiny4579 said:
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
Click to expand...
Click to collapse
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.

Tribulattifather said:
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Click to expand...
Click to collapse
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip

zachf714 said:
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
Click to expand...
Click to collapse
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD

zachf714 said:
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
How about the latest evervolv ICS release. That's what pure pulled from I believe.

@zachf714:
I will look also. If I find any, i'll upload them to the working folder i created for the project.
And if you guys find any, link me here and i'll download and do the same thing.
@tiny4579:
On the Luxe Rom we worked.. I don't have any of the files anymore. Do you happen to have a rom.zip of the project?
@project Community:
I've uploaded the Rom I used to port with to the dev host - droid in working folder.
I'm about to upload the other Rom I used.
Both the base and port rom I used to make the WIP are uploaded now.

Cm9 http://goo.im/devs/invisiblek/dinc/.../dinc-CM9-invisiblek-KANG-09-03-2012-1608.zip
This was actually the most stable ICS ROM I ran
Sent from my Nexus 7 using Tapatalk HD

I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github

zachf714 said:
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
Click to expand...
Click to collapse
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not until I just forked it and yeah you did

Damn. Wish I wasn't in bed already.
I'd compile pures git and see if his kernel does anything with the WIP.
My kid gets on the bus at 7:50a (est) and will Dev a bit before I get going for the day.
But if someone tries before then let us know the outcome.

I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.

Tribulattifather said:
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Click to expand...
Click to collapse
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2

zachf714 said:
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
That is exactly what I thought so took care of that hahaha.
Right now, imo, I'm thinking it's a lib problem from my recent logcat.
I'll hop on in a few minutes and take another logcat and upload it.
(I deleted the one I had because I hadn't realized that you all might want to take a look too)