Related
Amidst all the furore about the availability of 3 similar crossbow roms for the Universal, I have become increasingly amused by the number of comments from various people in the various threads, complaining about certain things not working, which sometimes work for others and then qualifying their complaints by saying that it is critical that the failing apps work on their devices and are desperate for help....
At the end of the day, if any of your apps are that critical then you shouldn't be upgrading - particularly to Crossbow, as it is very much in its infancy at the moment. I have no doubt that within a short while, the various Rom magicians here will have a number of alternatives available that are 'relatively' stable but anyone who depends on the functions of their Uni to the degree where they cannot survive without them should leave well alone....
Just my opinion
I entirely agree.
Guys, the WM6 roms should not be used.
If you happen to use it, backup first, bolt your windows, and suck it up if you loose your device, your data, or your innocence.
You will of course screw your warranty and a puppy will die. C'est la vie.
V
captainsensible2002 said:
Amidst all the furore about the availability of 3 similar crossbow roms for the Universal, I have become increasingly amused by the number of comments from various people in the various threads, complaining about certain things not working, which sometimes work for others and then qualifying their complaints by saying that it is critical that the failing apps work on their devices and are desperate for help....
At the end of the day, if any of your apps are that critical then you shouldn't be upgrading - particularly to Crossbow, as it is very much in its infancy at the moment. I have no doubt that within a short while, the various Rom magicians here will have a number of alternatives available that are 'relatively' stable but anyone who depends on the functions of their Uni to the degree where they cannot survive without them should leave well alone....
Just my opinion
Click to expand...
Click to collapse
I agree with you, it was the same situation back in the days when WM5 popped out
How true! By upgrading to WM6, you implicitely accept any shortcomings, bugs, missing functionality etc. Period.
(We should stick something along this line in a large fontsize on both the frontpage and the forum frontend. Maybe even in blinking red
Can I downgrade to WinCE 2.11 and get a version of active sync that will work on Windows for Workgroups 3.11 please?
Just want to make sure I am using something well established with all of the fixes, and years of background knowledge available for it
Oh, and I will need a serial to USB adapter so I can sync hehe.
Well, there are a lot of people around who want to upgrade to WM6 despite the fact that they have no idea what they're doing. If the average user sees an upgrade to a "New OS" they're probably more likely to give it a go than they would if it was just an upgrade for a bugfix or a re-arranged contacts database (rightly or wrongly).
The intelligent ones will do a bit of reading before deciding whether to even attempt the upgrade. But there will always be some who get themselves in a mess because they've rushed into it.
Fortunately, everything they need to know to get themselves out of their mess is on this forum somewhere - Unfortunately it seems many can't even be bothered to search - so the same old quetions are bound to be asked a hundred times over the next couple of weeks...Still, we all try to be helpful, don't we? (Even if it does get tedious at times!).
lol, no, it bugs the hell out of me, hence the reason I posted this http://forum.xda-developers.com/showthread.php?t=290234
I was a n00b once, I don't think I posted any lame questions, maybe some, I can't be bothered to go back and look, but from memory, it was only after I couldn't find it with the search that I asked somewhere.
I don't have anything critical I just have to run. Sure, there's software I have bought, and would be irritated if it didn't work immediately after an upgrade, but I am happy to take the risk, I have a Univeral and a Wizard, so I can always use the other if I have problems on one.
It's like this on anything though, something new comes out, everyone thinks they are an instant expert, messes it all up, and then begs for help because they were too lazy and stupid to read a few pages that would have explained it all to them.
Help, I just flashed my Universal to WM7 (Photon) that I downloaded from your website, and now it does not come past the bootscreen anymore ... I need my machine yesterday because my life depends on it, and I did not make a backup and now Microsoft has caused me to ruin my machine causing me to go out of business and you have to help me since I got the rom update from your website!!
(hehehehehe)
Well if you can get to the boot screen, all is not lost.
Get some superglue, and put a few drops into the USB socket.
Plug it in, and give it at least an hour to dry.
Now carefeully hold your device in one hand, and the cable in the other.
Now pull the cable out as fast as you can.
This shold prevent any further upgrading issues, or problems from ever happening to your device again.
Partially I agree, but i mean normal (lame) user who wants to upgrade only to show his palls couple of different # on boot screen. but i think helmi, ivan, indra or all else would never do good,working rom (like ivans aku 3.2, helmi 3.5), which are stable w/o feedback.
worst is here is helluva lot of people with prob."i tried 2 upgr. 2 wm6 & got COUNTRY ID err)
I love wm6 http email function. And somebody get the wm6 messenging in wm5?any hacks?
My mate sent me this, just some info that most people Know.
Testers of Windows Mobile Codenamed Crossbow (or Windows Mobile 6.0) have leaked at least 2 versions of the pre-release online,
According to our source betacollector the pre-release is incomplete, missing a few functions but working fine.
No Windows start orb here, that seems to be cropping up on everywhere on Microsoft software now, but then again WM6 is not yet final -who knows if that will be included in the final release.
The leaked version specs: WM6PreRelease.rar (54177kb) Build date 1/12/2006 (15341.4.2.0) Rom 2.00.02.pv / External Rom 2.02 PDAVIET
Theres also a second one WM6CB.rar weighing in at 59608kb for the MDA Pro / Universal or qtec 9000 that one is older than the above mentioned leak.
AlanJC said:
Well if you can get to the boot screen, all is not lost.
Get some superglue, and put a few drops into the USB socket.
Plug it in, and give it at least an hour to dry.
Now carefeully hold your device in one hand, and the cable in the other.
Now pull the cable out as fast as you can.
This shold prevent any further upgrading issues, or problems from ever happening to your device again.
Click to expand...
Click to collapse
Hahahahaha!!
Don't try this at home!!
I did an upgrade to WM6 on a fairly new 9000. Took me almost 6 hours to complete. The damn thing got stuck in the bootloader, lost my RADIo ROM, got it "bricked", managed to un-brick it again, lost my EXT. ROM, but at the end, it worked out and now the "damn thing" works fine on a brand new WM6 ROM. Exept for video calling and a few minor bugs I have no complains.....
Moral of the story. I am a man. Men like to do technical stuff. If you do not know what you are doing, stay off the damn thing. If you like to inflict pain on your self, but know what you are doing, just do.
Fooling around with some new gagets is cool. Sometimes it works out, sometimes it doesn't........
In my case, it worked out. Me is happy.........
AlanJC said:
Well if you can get to the boot screen, all is not lost.
Get some superglue, and put a few drops into the USB socket.
Plug it in, and give it at least an hour to dry.
Now carefeully hold your device in one hand, and the cable in the other.
Now pull the cable out as fast as you can.
This shold prevent any further upgrading issues, or problems from ever happening to your device again.
Click to expand...
Click to collapse
errrr .... will this speed up my UMTS connection? I tried searching the board on superglue+umts but I can't find anything ;-)
onlineemails said:
I love wm6 http email function. And somebody get the wm6 messenging in wm5?any hacks?
Click to expand...
Click to collapse
I thought it was great until I got two eMails in the space of 3 hours that caused it to crash when trying to view them...
Cheers,
Steve.
It got an limit for email for example 10kb and after that it doesnt get the email in full and you can request to get it full,
http://forum.xda-developers.com/showthread.php?p=1104565#post1104565
If anyone has any jailbreaking/ROM snatching ideas but are too afraid to use the software on their twom I can be your test dummy, a part of my phone broke and I got a new one. The broken one is still fully functional, just the mic doesnt work, however I can test any software or any trial runs of anything if needed, just post here
BTW i know there hasn't really been any progress in anything and nothing can really be done at all until we get ahold of a ROM or the drivers, just thought Id offer, since ive been paying attention to these forums for about seven months and haven't chimed in
How hard would it be to take a working ffc driver from android 2.3 and edit it to work with android 4.0+? It seems like it would be easier than writing a whole new driver from scratch. I searched the forum as well as google but could not find any other info on it. Is this feasible or is it not compatible at all. I have no experience with kernels, only slightly with C, so I'm not sure how it would work.
22andrew22 said:
How hard would it be to take a working ffc driver from android 2.3 and edit it to work with android 4.0+? It seems like it would be easier than writing a whole new driver from scratch. I searched the forum as well as google but could not find any other info on it. Is this feasible or is it not compatible at all. I have no experience with kernels, only slightly with C, so I'm not sure how it would work.
Click to expand...
Click to collapse
I'm not a dev but I suppose if the two existing drivers shared enough code and you were able to write from scratch what was different or missing it would be possible. I think actually problem is htc never has released the new driver publicly .
nrvlljr said:
I'm not a dev but I suppose if the two existing drivers shared enough code and you were able to write from scratch what was different or missing it would be possible. I think actually problem is htc never has released the new driver publicly .
Click to expand...
Click to collapse
yes. I knew they ceased development on the EVO without releasing anything (shame). Correct me if i'm wrong but the driver is held in the kernel? If there are any posts about the development of said driver, could someone point me to it? I would love to get involved into android dev. Thanks
22andrew22 said:
yes. I knew they ceased development on the EVO without releasing anything (shame). Correct me if i'm wrong but the driver is held in the kernel? If there are any posts about the development of said driver, could someone point me to it? I would love to get involved into android dev. Thanks
Click to expand...
Click to collapse
From what ive read you cant really do that since theyre two whole different OS's and you would have to start from scratch and build your own driver unfortunately. :/
So why can't that file(s) be taken from another phone? There are plenty that have 8mp Rear and 1.3mp Front w/720p Video. HTC Inspire,Huawie Mercury to name a couple. Both got ICS. I have came close to just flashing an ICS Ron and seeing if I could find the Camera for one of those and flash the files to see what happens. Problem is I don't know anything about porting. But,from all I have read the most important would be making sure the same brand Camera is used. I also suppose 4G would be borked but Wimax is dead so no biggie.
Fangstien said:
So why can't that file(s) be taken from another phone? There are plenty that have 8mp Rear and 1.3mp Front w/720p Video. HTC Inspire,Huawie Mercury to name a couple. Both got ICS. I have came close to just flashing an ICS Ron and seeing if I could find the Camera for one of those and flash the files to see what happens. Problem is I don't know anything about porting. But,from all I have read the most important would be making sure the same brand Camera is used. I also suppose 4G would be borked but Wimax is dead so no biggie.
Click to expand...
Click to collapse
The problem with just taking the camera app is that the driver is not contained in it. It would probably fc upon opening, let alone get all the way to the ffc. according to Wiki, drivers are either located in the kernel itself, or in "/system/lib/modules/" I have looked in the folder specified, and could not find the driver for the ffc, only wimax, and two files named "bcm4329" and "sequans_sdio". Im pretty sure those are not the ffc, but maybe if the kernel from a phone with similar hardware was reverse engineered, and the code taken from it, that would be the closest.
That's what I was talking about. I said files because not sure if it is a Kernel or some other form. I had downloaded Sabasa_Prime from here. I was going to take everything that had the word Camera attached and move it in via Root Explorer but the way I understand it that won't work. Is why I asked about someone trying to port the needed things from another phone.
Fangstien said:
That's what I was talking about. I said files because not sure if it is a Kernel or some other form. I had downloaded Sabasa_Prime from here. I was going to take everything that had the word Camera attached and move it in via Root Explorer but the way I understand it that won't work. Is why I asked about someone trying to port the needed things from another phone.
Click to expand...
Click to collapse
Oh, sorry. I didn't read that correctly. I'm not sure how similar the camera would need to be in order to steal its driver. It seems like it could work, however in reality, the hardware is connected differently passing through different circuits, but that could be solved by looking at how previous versions of android calls for the camera. If I only had the time and patience I may take a peek into the kernel when I get home from vacation.
The Rom is designed for the Desire HD but there is an accompanied file for the Inspire users. Not sure what is in them because I never opened them. Wouldn't really know what I was looking at anyway. I did however search and compare them aide by side and that is the one thing the Inspire and EVO have in common,Cameras and Video quality. But,I believe I also read somewhere that they must also be the same brand hardware and I have no clue on how to find that out. I tried to search but no luck. I mention it because I am sure there are those around who have the knowledge to know if that matters and how to find out if they share the same hardware if it does.
Fangstien said:
The Rom is designed for the Desire HD but there is an accompanied file for the Inspire users. Not sure what is in them because I never opened them. Wouldn't really know what I was looking at anyway. I did however search and compare them aide by side and that is the one thing the Inspire and EVO have in common,Cameras and Video quality. But,I believe I also read somewhere that they must also be the same brand hardware and I have no clue on how to find that out. I tried to search but no luck. I mention it because I am sure there are those around who have the knowledge to know if that matters and how to find out if they share the same hardware if it does.
Click to expand...
Click to collapse
That's what I thought. I think the closest we can get is taking a kernel from a phone with similar hardware, taking a kernel from the evo with a working ffc, look at how it's called for, combine that with the code from the kernel from the other phone, and that would get you close. I will see how similar the code is for the ffc, and see what I can come up with.
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
Title is the question. Please no negative/hate towards W10M, for which I am saying don't even reply. You would have to experience Windows Phone for 1+ year to even get a say to feel what i feel about windows OS. Android is still ugly lol. Anyways this is my "Opinion" on this matter.
I only want to know if it even is possible to do such thing for which this phone hardware is compatible for the features it has with the OS. Just the matter of drivers? I'm no software developer but is why i am asking you guys of possibilities of this happening or not.
Thanks!
Shawn
Not...
As you said drivers are a big issue... You might get away with the generic drivers for audio and video, might, but you will probably need specific drivers for the modem so goodbye phone hello pda...
More than likely it just won't boot...
You'd think with all these phones being released that have nearly the same chips (such as SD820 etc...) and antennas... but at same time would think W10M would be just like PC version, download needed drivers to operate the hardware lol.. But just what every company wants, to make everything different from each other to make more money.
Yep, that's what it's all about... To make $$$$...