Database Users

[Q] long time watcher and rom user. first time poster.

Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel

Tell us what your problems are here.

1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium

Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple

Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.

shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel

Insanity

Hello Everyone!
I just want to say some words about my experience with Insanity.
I got my sgs ~3 months ago and i tried a almost all the cooked roms.
I started with darky, that was the first I've installed then I found this forum and tried almost everything(only GB roms).
but I sticked to insanity cause thats all i want very simple only a few apps are installed and its kinda fast.Then I realized that this blueish screen is awful. I started to look after kernels with voodoo color. first i tried glitch that caused my first BSOD i was very scared but I then i was able to fix it. Then I used Fugumod for a while that was allright original CM led notifications worked perfectly it was fast but I had some problems like when I charged my phone the screen became funny i have to pull off the cable to be able to write a sms message. Then the new neo18 kernel came out that's almost perfect led notifications work voodoo color gives amazing screen and until now my only problem is when I'm outside so the temperature is low like minus 1-5 the android.com process gives FC and I cant see my contacts.
So i really like insanity as a rom but i want to hear others experience about it.
So far my problems are:
Viber stopped working i dont know why i cant remember what change made it cause lot of things happened changed to new insanity cm51 as i remember new viber came out. I can't get it work with stock fugu or neo kernel
The other big problems is sometimes when i answer a call they cant hear me or i cant hear them for the first time then i call them back and everything works fine.
Can somebody give me any advice to solve these problems?
please dont be rude I'm not a complete noob but Im not a developer either.
Thank for anyone who helps
PS.: if you give me any advice whats the best kernel for insanity in your opinion i will be happy

[Q] Query for acer900 re Jazzman's Rom 1.3

Acer900
Don't know if you're still even active in these forums but just wanted to say a huge thank-you for your ROM and as I can't add a message in the developers forums yet, I wanted to add my thanks here!
It is the only custom rom I can currently DL for the S200 but it's absolutely amazing and its like being given a whole new phone to play with. Huge respect for you and your work and I hope you might not be entirely ready to give up on the phone just yet...
I do have one problem however. I flashed your rom from a "virgin" 3.003c firmware and enabled EZinput for full landscape mode. So far so good. everything worked until I went in to the camera - half screen viewfinder displayed, no icons at screen edge and (after 30-40 seconds) the display locked and no hard or soft keys were able to get me out of camera mode. I couldn't even get it to power off, I had to pull the battery and restart. I read in the developers forum that the camera is a source of problems and at one point brainmaster had posted a cab file to reinstall the acer default camera so I installed it and restarted the phone but when I went into the camera again, the exact same thing happened.
Other posts seem to suggest it may be an HTC keyboard/camera conflict but presumably many folk on custom roms got that camera to work to some degree.
Any suggestions you can offer? I don't need it to work perfectly. I don't take that many photos on the phone but I do use it occassionally and I can't use this as a daily rom if locks up every time I accidentally start the camera.
Thanks again. Really appreciate all of the hard work you've put in and this rom does really make an old device sing very sweetly once again.....
BelfastLad

BelfastLad said:
Acer900
Don't know if you're still even active in these forums but just wanted to say a huge thank-you for your ROM and as I can't add a message in the developers forums yet, I wanted to add my thanks here!
It is the only custom rom I can currently DL for the S200 but it's absolutely amazing and its like being given a whole new phone to play with. Huge respect for you and your work and I hope you might not be entirely ready to give up on the phone just yet...
I do have one problem however. I flashed your rom from a "virgin" 3.003c firmware and enabled EZinput for full landscape mode. So far so good. everything worked until I went in to the camera - half screen viewfinder displayed, no icons at screen edge and (after 30-40 seconds) the display locked and no hard or soft keys were able to get me out of camera mode. I couldn't even get it to power off, I had to pull the battery and restart. I read in the developers forum that the camera is a source of problems and at one point brainmaster had posted a cab file to reinstall the acer default camera so I installed it and restarted the phone but when I went into the camera again, the exact same thing happened.
Other posts seem to suggest it may be an HTC keyboard/camera conflict but presumably many folk on custom roms got that camera to work to some degree.
Any suggestions you can offer? I don't need it to work perfectly. I don't take that many photos on the phone but I do use it occassionally and I can't use this as a daily rom if locks up every time I accidentally start the camera.
Thanks again. Really appreciate all of the hard work you've put in and this rom does really make an old device sing very sweetly once again.....
BelfastLad
Click to expand...
Click to collapse
First,
I'm glad that the rom is working for you, Thanks!
second,
I'm no longer actively building after my PC's Hd mysteriously crashed and I lost everything before that I was in the process of upgrading the rom to v.1.3.5
and trying to find a solution to the problem you're experiencing now.
It has nothing to do with the keyboard/camera relationship.
The Full Rotating phone canvas I used was developed for HD2 leo, not acerS200
meaning, it uses components native to the HD2 leo in this case, it's camera,video,full screen viewer etc... our problem w/S200 is that the camera,video,picture viewer etc.. being acer components,not HTC Leo's,
function using their own specs,dimensions, and most importantly, it's own resolutions and rotation based on those size resolutions.
I was experimenting with the phone canvas to see if there was a way to separate our acer camera,vid., but lost my HD... as a matter of fact,
I'm using a V.1.3.5 beta in my phone now that has parts of different phone canvas versions i.e. Raphael,Laurentius, Parts of caller ID fixes from laurentius too. But my testing was cut short and I haven't the time or desire to start all over again, sorry
So to finally answer your question, You must " uncheck" "EZinput" under G sensor settings for the camera and video to function properly.
Maybe one day I'll replace my PC's HD and try to cook again but I'm thinking
that it may be easier to buy an "acer stream"('cause I like acer) and see what
that's like.
Thanks

Thanks for the reply.
I really appreciate all the effort that went in to making something as good as this but appreciate that sometimes with technology we all just need to "move on".
I'll look forward to seeing your name (and efforts) pop up elsewhere in the forums.
Cheers.

[Q] LG G2 D802 Black Screen

Guys i have a problem with my LG g2 D802 with screen turning black often, then i messed around with the phone and ticked the option "always GUP overly" something like that in developer menu, anyways after that i didn't had any problem for 3 days, then again the blackout started,after restarting the phone more than 10 times i got the display back, then i checked if that overlay option is still ticked, is wasn't ticked , and i didnt touched it, anyways ..this should be an software problem right? anyone here know how to fix this ? Help me out please
Best Wishes

@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.

wulsic said:
@Demitha some options in developer options resets after boot so they are getting unticked by the system itself. I don't know why your screen turns black after enabling that option, the onkly thing i can say to try is to wipe cache/dalvik-cache and even maybe an factory reset and if those things doesnt work then reflash stock.
We could also see maybe what caused an bsod when you logcat but since it appears often its hard to say when you need to start logging.
Click to expand...
Click to collapse
the option name is "disable HW Overlays" screen dont turn black after enabling that option, i meant,screen didnt blackout after enabling it, but yet some times screen goes out, i did reset the phone once, didn't fix the issues, how do i reflash a stock? i never done it?is there a video guide or something? help me out please.
Best Wishes

@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?

wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
yeah it was worse before,after enabling that option blackout didnt happen fro o 3 days , i noticed even though i didnt restart the phone that HW overlay option gets unticked :/

@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.

wulsic said:
@Demitha well if it was even worse before then i suggest you to charge your phone to 80-100% for safety because it may take a long time, maybe it can be lower but for safety I always have my battery around that percentage. And then you can try the guide. If your screen turns black can you touch it on random spots to see or it makes sound noises like if you click on anything.
Click to expand...
Click to collapse
i hear sounds and vibrations, phone is totally working on the blackout

@wulsic you think reflashing will fix this issue?

@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.

wulsic said:
@Demitha here is the guide if you didn't founded it yet: http://forum.xda-developers.com/showthread.php?t=2432476
Did you had this blackout also before enabling it?
Click to expand...
Click to collapse
wulsic said:
@Demitha it could be but i am not sure, it could be also an hardware defect maybe, and also maybe an software so try to reflash it I am not sure or its hardware or software since it could be both.
Click to expand...
Click to collapse
if i flash the phone,i will get software updates like normally ?

@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?

wulsic said:
@Demitha if you flash the phone to 4.4.2 then you will still get software updates for apps, system incremental updates etc so dont worry about it. You need to care first more to find out the black screen problem. Also if you have an blackscreen do you see like an backlight on ? That the black color gives light ?
Click to expand...
Click to collapse
yes it does, it like a black light,not very bright but the light is there

@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.

wulsic said:
@Demitha ahh okay so its not totally off, it could be an software problem since i also had something like that on custom roms when waking up my device (bsod) but i dont remember that my touchscreen still works that i hear those noises so it could be also an hardware problem. The only thing i cannsay is flash it to stock once again like it came out of the box and use it for a couple days to see or its coming back. If so can you reply again to this thread? I think that some g2 users could maybe say more about this subject since i dont have the g2. I also read about display graphics ram which saves battery by holding an image and displaying it like that instead of the gpu so i thought maybe that it got bugged or what, correct me if i'm wrong I read it today in the morning around 2 am.
Click to expand...
Click to collapse
well, i never flashed a phone before, im afraid i might do it wrong

@Demitha i know that you are scared for the first time, when i flashed an android phone for the first time (Htc google nexus one, i miss the trackball xd) i read everything carefully and i did it good it was different then windows mobile since i was the first android user in my family. but i had it for some weeks and sold it again because i had touchscreen issues,power button didnt worked so yeah. But that was some hardware issue which wasn't caused by the flash but it was the previous owner.
So just read the guide carefully, backup all your files to be sure and charge your phone to 80% atleast thats what i am always doing. Or you need to know an geeky friend who also do these stuff

can you please point out what i need to download in order to flash the phone in this thread, there are different versions of g2 models there ,please check the screenshot below
https://copy.com/71RAumYBzgmI

here is the other screenshot, - https://copy.com/9oNye3tlH96z

@Demitha you said you have the d802 version and i also see in the build/software number the d802 so
You need to flash the d802 version which is the international one so just find the d802 files and flash it goodluck! Reply if you need help again

[SOLVED] Weird Phone app behaviour when trying to make a call on custom ROMs GT-I9506

Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.

If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.

DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?

henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?

DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads

Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.