libhtc_ril.so segfaults - HTC Wildfire S

Here is what I learned about libhtc_ril.so.
CM7 and my CM9 port (up till now) use a libhtc_ril.so from liberty. On CM9 it looks like this library is responsible for the battery drain as everything is fine in airplane mode.
So I've started to copy the latest libhtc_ril.so form marvel stock rom and tested it. It segfaulted so I've started to attach strace to find out what's going wrong. I've fixed some permissions and it worked, but as soon as the screen turned off it segfaulted again.
Another strace showed that it segfaulted while trying to open /sys/devices/platform/msm_hsusb/usb_function_switch.
I've implemented that function in the kernel and it still segfaulted and I had no idea what to do now. Today I analyzed the RADIO logs and stumpled upon:
Code:
D/RILJ ( 328): [0100]> SCREEN_STATE: false
D/HTC_RIL ( 1360): ril_func_screen_state_notified():called
D/HTC_RIL ( 1360): ril_func_screen_state_notified():Not found 'ether:' in USB_STATE_PATH
As it segfaulted directly after closing /sys/devices/platform/msm_hsusb/usb_function_switch it smelled like it expeced to have something like:
Code:
ether:disable
I've dived into the code with Droste and we found out that in our tree it was called rndis and in the htc tree it was called ether. We also forgot to update a header file. However after it found 'ether' in the out in the output of /sys/devices/platform/msm_hsusb/usb_function_switch it started to work just fine.
I hope this post will help other developers with similar problems.
This is the full set:
Code:
ether:disable
accessory:disable
usb_mass_storage:enable
adb:enable
cdc_ethernet:disable
diag:disable
modem:disable
serial:disable
projector:disable
THANKS AGAIN DROSTE

This will definitely help in better CM7 and CM9 builds!!!! You are awesome dude!!!!

I dig that this is a dev convo, and appreciate what happened here. But this stuff was better said in an irc....

BigChillin said:
I dig that this is a dev convo, and appreciate what happened here. But this stuff was better said in an irc....
Click to expand...
Click to collapse
How should another developer running in the same problem find the solution if we talk about solutions in private IRC channels?

modpunk said:
How should another developer running in the same problem find the solution if we talk about solutions in private IRC channels?
Click to expand...
Click to collapse
Agreed.

BigChillin said:
I dig that this is a dev convo, and appreciate what happened here. But this stuff was better said in an irc....
Click to expand...
Click to collapse
Dude even though I don't know anything about programming or whatever......I still understood about 70% of it.....it's not that complicated

BigChillin said:
I dig that this is a dev convo, and appreciate what happened here. But this stuff was better said in an irc....
Click to expand...
Click to collapse
Or you could stay out of the dev threads. No one's forcing you to read it. Back to business.

also some of us who are learning find it helpful and interesting
cm7 soon to be cm9

really really interesting thank moodpunk, just a question
libhtc_ril.so now is fixed for all version of radio or just for a specific version? in another thread you said that your phone has 47.23a.35.3035H_7.53.9.03M that according to RUU isn't the latest radio version. so i'd like to know if on the newer version (47.23e.35.3038M_7.57.39.01M) it will segfault or not. thanks

d33ps1x said:
Or you could stay out of the dev threads. No one's forcing you to read it. Back to business.
Click to expand...
Click to collapse
That's cool, pretend you're dev. Then pretend you've read the rules of the dev section: http://forum.xda-developers.com/showthread.php?p=15972725. I was being nice because modpunk deserves that. I don't need YOUR half a cent though.
Edit: reread the rules myself and have found myself wrong. Flame on!!
Sent from my HTC_A510c using Tapatalk 2

BigChillin said:
That's cool, pretend you're dev. Then pretend you've read the rules of the dev section: http://forum.xda-developers.com/showthread.php?p=15972725. I was being nice because modpunk deserves that. I don't need YOUR half a cent though.
Edit: reread the rules myself and have found myself wrong. Flame on!!
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
Nah. Be well.

Related

Compiling Android for the Epic.

Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.
+1 on this.
+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel
I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!
I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...
yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[Q&A]["Spamming and ETC :)"]CyanogenMod 9.0.0-GalaxyICS

Hello everybody here,
so lots of us said that we should have a "Spamming" thread for CM9 and 4.0 Android development made by Maclaw's DevTeam-thanks for them, again . So here it is:
Please guys, if you have any bugs and problems which are already mentioned in GitHub, but you don't care to "ask-first-then-shoot", then post your problem here.
Please, write here, and really, don't annoy dev's on their DEV thread. That's for them to submit upgrades, news, and stuff.
Thanks anyway, and please, let the Dev's work in the calm way it should be.
Spam and post your heartbreaks here
Thnx for the thread. I feel like I can post my non-contructive post yet not clutter the dev thread
I following/trying CM9 closely. It looks very promising can't wait for the finished ROM
I should make some time to properly test/bugreport in git.
Should be in general, not there.
Wysłane z mojego GT-S5660 za pomocą Tapatalk
shiftyHungary said:
Hello everybody here,...
Click to expand...
Click to collapse
have u ever thought, that 'tards constantly flaming and making EXCEPTIONALLY unnecessary threads such as this one, are in fact much worse than noobs whining about their gallery not working?
Seriously though, I've been following Maclaw's thread for weeks, and the spam is no where near annoying as some "certain efforts" to end it.
Haters gonna hate, noobs gonna noob, deal with it.
p.s i consider myself a noob as far as android goes. But i don't whine about it, and don't shout at people on forums.
p.s2 somehow I doubt that this message will make the impact I intended it to make... sad.
Oh, and another thing - how do you define "spamming" and it's relation to the original post? I'm not much of a linguist myself, but something tells me you're not either, therefore both of us should keep our mouths shut...?
Oh 2.0: did i mention that this whole thread is a spam? ( and what is it we do with spam nowadays huh? )
You made good points. I don't spam myself as I see others do. At first I thought this was a good idea. So the course of action is to kill this thread or let it die.
Last post.
o0ze said:
You made good points. I don't spam myself as I see others do. At first I thought this was a good idea. So the course of action is to kill this thread or let it die.
Last post.
Click to expand...
Click to collapse
actually I did, see cm9 thread
I thought maclaw would make one because he hates the spammers, so I suggested this, just like the ace forum
sent from my Samsung Galaxy Gio using XDA premium
how about fixing 3d graphics in future? Now, Asphalt 5 is laggy on my Gio.
same as inotia, cant play currently
but that will be fixed when the rom features work flawless
sent from my Samsung Galaxy Gio using XDA premium
feiks- if you dont feel that this therad is necessary, then ignore it. there are some people who think this is a good one, although Maclaw is right, this should be in general.
And yes, spaming the DEV post is something like the whining of ~15 people that gallery is not working, camera is not working...if they'd read first, then they would know what they can get from this rom.
Though, ignore this post if it's unnecessary for you.
For the others, enjoy.
A quick point about creating new threads and where to place them.
Question.
Are you actively developing something?
Answer.
Yes.
Result.
Thread should go in the Development section
----OR----
Answer.
No.
Result.
Thread should go elsewhere.
Click to expand...
Click to collapse
Intentionally creating threads in the wrong place, just annoys other users and creates work for me. In future think about where to place your thread.
If after creating a thread you think, "I should of posted that in 'General'". PM me or report the post, I'll happily move it.
Thank you
It was my fault to place it to development.
TTS
Loving the ICS ROM by Maclaw and the gang - awesome work - it keeps getting better and better with each release.
Android is new to me so still learning - trying to get text to speech working, of course to try out a Siri like app.
I cannot seem to find where to turn on text to speech. I have tried a couple of apps and it appears that it is not on - and I cannot find where to turn it on.
Thanks in advance for any help
G
gw22 said:
Loving the ICS ROM by Maclaw and the gang - awesome work - it keeps getting better and better with each release.
Android is new to me so still learning - trying to get text to speech working, of course to try out a Siri like app.
I cannot seem to find where to turn on text to speech. I have tried a couple of apps and it appears that it is not on - and I cannot find where to turn it on.
Thanks in advance for any help
G
Click to expand...
Click to collapse
Theres some app called talkback on stock roms, dont mnow how it works
Sent from my GT-S5660 using Tapatalk
Finally I can say something about CM9 and ICS. I've been quietly reading the development thread from the beginning and thanking developers' posts for many months.
Anyway, I read that next release will be faster and with more working settings. I can't wait to try it out. I tried Beta 2, because it got generally good feedback before, and I thought that maybe it is good enough for daily usage. True, it is functional enough, but just a bit too laggy and glitchy for my liking. It was a good experience to test it, and all in all it didn't seem that much different from Gingerbread afterall. I miss the ability to put widgets on homescreen by simply longpressing, now you have to go to app drawer and search there - but I'm sure I will get used to it in time. I like the new setup of settings menu though.
But my message to the development team and everybody else who helps them: Good luck and thank you! I will continue "thanking" your posts in the dev topic. We are lucky to have active CyanogenMod developers on our rather not-so-good and not-so-popular phone, and good developers too - Phiexz and Maclaw as the main men, but also others. Kudos.
Im dreaming about 3.0.8 kernel (or new) on ics 4.0.3 on Gio
If i get a new sms the phone wont viberate..
I have the silent profiel turned on but still normally i would hear the viberating sound getting a new message. This is a bit anoying cose often i have to react right away.
Any one know how to turn on the viberating?
Hi,
I installed beta3.
I can't download s2e from the market. Is any version that works with cm9?
Thanks
The betta 3 is a lot better alread. Things that dont work for me atm are: Camara (I did try other cammera apss to. No succes) The foto galary app will crash (I only have like 280 fotos. Kids there fun)
Playing movies (Xvid/divx) and mp3 does not really work well.
Thats it for no.. Got to work again.
Why Spam?
Just help Dev friends. Your support would encourge them to work hard on softwares. Sorry for bad bad english
There is a discussion in CM9 development topic about bootlogos. Am I the only one who doesn't care about it? I've disabled it anyway for faster booting. Why is bootlogo so important for some? For all I care it could be a steaming dog turd, it doesn't matter

Weekly ICS ROM Updates

Hi all,
I am going through all the threads that have ics based roms for our phone and thought it might be a good idea if we had a communal collation of all ics roms that are active in this forum with provided chainlogs and small reviews of said rom and what issues they have.
Reason for this is simple, to help other users that are not confident in flashing up to 4.0.3 unaware that they may run into something that they did not bargain for.. Hopefully this way we
A) Get a general run down each week as to what rom is working well which are not.
B) Issues/bugs.
C) Reviews of what works and not.
D) Temp fixable issues ie: auto rotation.
E) May help in less clutter in actual development thread.
I thought I would put this out see if anyone agrees here. I am more than welcome that if we use this thread as a starting point.
In no way shape or form that this thread will be used as a means of competitiveness between devs, to start flaming in any sort of fashion, this is purely a thread designed to help everyone with ics progression where its at, what dev's are up too and which would be safe to flash and what is not and is for experimental use.
Hopefully this could be a useful thread, with the dev's permission in doing this of course
Cheers.
I like the idea
+1 to this idea!!
There are already Q&A threads for each of the ROM's. Why make the board more cluttered than it already is by re-posting what is already in those threads?
People need to learn to use the search function and stop being lazy and actually take the time to read a thread every now and then. A thread like this will do nothing but enable the lazy to be even less productive and will not help. You will just see the same questions asked here over and over and over and over and over just like in all the other threads.
Also if people would read a damn OP like they are supposed to before flashing a ROM they would already know what does and doesn't work and if the ROM is a RC or experimental.
+1
Sent from my SAMSUNG-SGH-T989 using XDA
DannyB513 said:
There are already Q&A threads for each of the ROM's. Why make the board more cluttered than it already is by re-posting what is already in those threads?
People need to learn to use the search function and stop being lazy and actually take the time to read a thread every now and then. A thread like this will do nothing but enable the lazy to be even less productive and will not help. You will just see the same questions asked here over and over and over and over and over just like in all the other threads.
Also if people would read a damn OP like they are supposed to before flashing a ROM they would already know what does and doesn't work and if the ROM is a RC or experimental.
Click to expand...
Click to collapse
Valued response, and yes using the search tool does help, but. rather than searching for what is needed why don't we have one thread to sum up on all progression? This thread is not designed to have countless questions all this is to gather weekly updates on ics roms from there respected developer. If someone wanted to ask questions they should be directed to the respected Q&A thread as they have there own. If someone wishes to choose to read up on what is happening in the world of ics t989 development then they come here nothing more nothing less.
As this wouldn't be hard to do at every week commencing someone can be anyone can choose to post up any sort of update to any rom and that is valid for that week only... then make up another thread so for example this one wouldn't spiral out of control and inform a mod to delete or close thread... simple that way it would stay fresh relevant with what we want to know, and of course anyone can participate in this.
Again thanks for your input, I'm not saying this is what we should be doing but a suggestion to everyone and see if this would make life a little easier on some. Alternatively if you don't like it then don't post anything worth mentioning and leave for people who could benefit from it
Cheers.
Issues for all ICS Roms outside xRavers AOSP
Autorotation
Possible Issues:
Echo Call
SMS Fail
Gallery Problems
Shutdown Issues
xRaver AOSP -> see xRaver AOSP thread
Pretty much covers it Can end thread pretty soon.
Is anyone working on a ics kernel for our devices?
Sent from my SGH-T989 using Tapatalk
tdizzle404 said:
Is anyone working on a ics kernel for our devices?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
i am based off the skyrocket sence we dont have **** for our device....
RaverX3X said:
i am based off the skyrocket sence we dont have **** for our device....
Click to expand...
Click to collapse
Cool how's it coming along?
Sent from my SGH-T989 using Tapatalk
RaverX3X said:
i am based off the skyrocket sence we dont have **** for our device....
Click to expand...
Click to collapse
Hi RaverX3X , and would you mind others or yourself would post up on your current progression of your ics roms and their chainlogs and known issues so that way people who this need only to see the basic stats and if it is suitable for daily use?
Cheers.
Sent from my SGH-T989 using XDA
tdizzle404 said:
Cool how's it coming along?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
not as fast as i like but then agian i dont have a whole lot of time to work on it if i could do it 24/7 365 lol prob would have had it done or further then i am now
Agera said:
Hi RaverX3X , and would you mind others or yourself would post up on your current progression of your ics roms and their chainlogs and known issues so that way people who this need only to see the basic stats and if it is suitable for daily use?
Cheers.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
4th post has the chainlog... or third i dono ll go look lol
Gallery Workaround
jim93 said:
Issues for all ICS Roms outside xRavers AOSP
Autorotation
Possible Issues:
Echo Call
SMS Fail
Gallery Problems
Shutdown Issues
xRaver AOSP -> see xRaver AOSP thread
Pretty much covers it Can end thread pretty soon.
Click to expand...
Click to collapse
To replace my battery and my camera since it force closes, I use QuickPic as my gallery and Camera zoom FX Pro as my camera. They work pretty well with some minor set backs.
Echo?
Are there any ICS ROMs that do not have an echo????
It seems to be an issue with the flashing process as far as echo goes...easy does it, my DD has no echo...actually while many people have reported that among other bugs the only one I have is the reboot hang...which really...tough **** I have to hold the power button down the few times I need to turn it off lol. Oddly though it does not hang if I reboot into recovery from rom manager.
Ics is really weird...everyone is getting different bugs following the same install process. I'm guessing some of our devices are more willing to adapt to the skyrocket kernel than others...
zander21510 said:
It seems to be an issue with the flashing process as far as echo goes...easy does it, my DD has no echo...actually while many people have reported that among other bugs the only one I have is the reboot hang...which really...tough **** I have to hold the power button down the few times I need to turn it off lol. Oddly though it does not hang if I reboot into recovery from rom manager.
Ics is really weird...everyone is getting different bugs following the same install process. I'm guessing some of our devices are more willing to adapt to the skyrocket kernel than others...
Click to expand...
Click to collapse
Guess you got the one with the magic bean.
Well before I went on vacation Tuesday I was playing around with a few of the different ics that are there for tmo gs2 and found that a lot of issues went away when I unmounted the SD card. The camera had no problem and I didn't notice any echoed sound. Kind of strange but one thing I noticed that a lot of native ics devices don't have external SD cards. Might be something for devs to look at.
Sent from my Galaxy Nexus using Tapatalk
retrofred said:
Well before I went on vacation Tuesday I was playing around with a few of the different ics that are there for tmo gs2 and found that a lot of issues went away when I unmounted the SD card. The camera had no problem and I didn't notice any echoed sound. Kind of strange but one thing I noticed that a lot of native ics devices don't have external SD cards. Might be something for devs to look at.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
tried like you said... not true on my phone... either way it does not work.
Rather than start another thread, while perusing the amaze forum I stumbled.upon info on CM9..
According to this https://plus.google.com/106544349933037831956/posts/4Lpyw9bPBCq
Which is the Google+ page of the dev in charge of maintaining CM9 on the amaze, no cyanogen dev is currently.working on our device. Sad to see but figured I'd share for those ccurious
Sent from my Real Gs move in silence like lasagna

[ROM] MIUI Port

This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409
Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?
If you want mae some cool port, i thikn sense rom is good candidate...
Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far
Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.
Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support
uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?
jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video
uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?
jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.
uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.
justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.
good luck
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:

Categories

Resources