Originally Posted by pixut
I have graphic issue with the ICS leak. Everything is fine and smooth at first. However, I can't use the phone if I turn off the screen and turn it on again because the screen looks like a lost-signal TV. Something likes that . My installation procedures: motofastboot full wipe then flash boot, system and vendor.img. I also try CMW zip of upndwn4par, epinter and lokifish but none of these work.
My tegrapart is 1100:100:800. AT&T atrix.
By the way, I have SOD with whatever rom I use after unlocking bootloader. Does it relate to graphic issue above?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the same problem. Help solve the problem ....
update:
video1
video2
video3
video4
file quiz
| MB860.ATT.en.US | ReservedOdm 10000000000010001000300004000 |tegrapart=mbr:1100:100:800 |
xxcombat said:
Originally Posted by pixut
I have graphic issue with the ICS leak. Everything is fine and smooth at first. However, I can't use the phone if I turn off the screen and turn it on again because the screen looks like a lost-signal TV. Something likes that . My installation procedures: motofastboot full wipe then flash boot, system and vendor.img. I also try CMW zip of upndwn4par, epinter and lokifish but none of these work.
My tegrapart is 1100:100:800. AT&T atrix.
By the way, I have SOD with whatever rom I use after unlocking bootloader. Does it relate to graphic issue above?
I have the same problem. Help solve the problem ....
| MB860.ATT.en.US | ReservedOdm 10000000000010001000300004000 |tegrapart=mbr:1100:100:800 |
Click to expand...
Click to collapse
tegrapart=mbr:d00:100:800
you are not alone.
Guys, can you type here your full tegrapart line along with kpanic line too? I'd like to investigate more about this issue
ex: tegrapart=mbr:d00:100:800,kpanic:2100:400:800
ex2: tegrapart=mbr:1100:100:800,kpanic:2500:400:800
tegrapart=mbr:d00:100:800,kpanic:2100:400:800
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA20703..
upd
A small survey data from our forum (tegrаpart- graphic problem)
1100 all ok - 9 person
1100 graphic problem - 6 person
d00 all ok - 15 person
d00 graphic problem -1 person
I guess it's because we have displays from different manufacturers.
tegrapart=mbr:1100:100:800,kpanic:2500:400:800
international atrix. I don't have graphic issues apart for the camera that shows purple lines on the bottom...
Random reboots occur very often instead and they are really annoying
lightlord said:
Ok, i have the other tegra part but same issue. I go arround this by putting phone into dock or connect it to tv via hdmi and the screen magically
stabilizes. So what i do is:
When booted with the garbled screen i:
-conect to lapdock and open the lid,
-wait a few seconds, on laptop screen there is some out of phase webtop screen (on my bravia hdmi screen gets perfect at that moment)
-i close the lid on lapdock, the screen on phone digitizer reapears stabilized with unlock circle
-i unlock and disconect the phone and it works till next reboot. mileage may vary from 9 hrs to few minutes when connecting and disconnecting a tv via hdmi
Click to expand...
Click to collapse
anyone can confirm this?
So this could be an issue with webtop? :S
Should we do a depth-in debugging with logcat when putting the screen off?
try to remove all /system/lib/hw/sensors*
don't solve the problem, but I think something changed ...
jhonnyx said:
So this could be an issue with webtop? :S
Should we do a depth-in debugging with logcat when putting the screen off?
Click to expand...
Click to collapse
Can't be webtop or otherwise the "Somebody's" CM10 wouldn't have the same issue.
As far as the heat issues. Is everybody seeing this on the bottom near the speaker? If so, the radio and flash memory are in that area.
Got the graphic problem too. :\
tegrapart=mbr:1100:100:800
Could it be related to parts of the leak people have or haven't flashed? I flashed all .img files as outlined in the .bat other than motoboot and that was only due to an error. I noticed many instructions only suggested flashing the main .img files like system, preinstall, webtop and boot but there were several more. These may not be included in the .zip files created either.
Sent from my Thunderbolt using xda app-developers app
And did you have any problems?
Not one single problem related to the display glitches. I have had a mostly stable experience but I am also running wifi only without a simcard. I have had maybe a total of two reboots since the leak.
Edit:
I don't have a lap dock and have yet to try out my HDMI cable to my LCD. No other docks except for car dock.
Sent from my MB860 using xda app-developers app
This is what sucks to thing about. We have this probably relatively old build we use to try and get stuff working..there might be extremely later builds with everything working great just no leak for it.
someone tells me change the DPI from 240 to 242 . 6 people find it worked. i hope it may helps you
I notice in the OP there was no mention to flash the preinstall or recovery .img files. I believe these files have necessary functions on first boot. I wonder if it is an incomplete flash or something related to the radio or both?
Sent from my MB860 using xda app-developers app
xxiaoxinjiang said:
someone tells me change the DPI from 240 to 242 . 6 people find it worked. i hope it may helps you
Click to expand...
Click to collapse
more details...
did they have graphic problem?
upd
I changed 240 to 242 in build.prop - that did not work ((
JPBeard21 said:
Could it be related to parts of the leak people have or haven't flashed? I flashed all .img files as outlined in the .bat other than motoboot and that was only due to an error. I noticed many instructions only suggested flashing the main .img files like system, preinstall, webtop and boot but there were several more. These may not be included in the .zip files created either.
Sent from my Thunderbolt using xda app-developers app
Click to expand...
Click to collapse
Can you list the specific .img files you had installed? Or, let me try listing and can you confirm? lol.
boot.img, preinstall.img, radio.img, recovery.img, system.img, vendor.img
Thats what I see from another download I have called "olympus-userdebug-4.0.4-6.7.7_95-95-test-keys-ATT-US - 7.5.0.83.zip"
Seems like with CWM I shouldn't be installing recovery.img though, right?
Should I keep radio.img?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Photon Laser provides an optimized Motorola Blur base for your Photon 4G with Sprint. Almost everything is 100% stock, but there are a few optimizations packed in that will make this pseudo-ROM worth your while.
Code:
- Based on the latest Motorola leaked SBF
- Max events per second (better scrolling)
- Proximity sensor modified
- GPU fix (better graphics in some applications)
- Increased VM heapsize
- Increased WiFi scan interval (battery life)
- Widget Grouper
- Motorola only bootscreen
- Ad blocking via “hosts” file
- Deodexed
- Zipaligned
- PNG optimized
- Webtop-over-HDMI hack (thanks _unknown!)
- SD card speed hack
- Memory killer hack
- Google Talk with video
Click here for downloads
Follow the installation instructions.
Follow me on Twitter for more information!
_unknown
Webtop modifications
Fenrir/Ririal
Build.prop fixes
Juwe11
RAM optimizations
nikademus
FuguTweaks
Yay 4 Juggs
Leaked SBF
Why is my device running/booting slowly?
Your first boot will take an unimaginably long time. After that, your device will continue to run slowly until the application cache is built up. Don't worry, the speed will increase as you use the ROM!
The new Android Market doesn't work for me. Can I get the old one?
Yes! Check the attachments on this thread. Download and install "androidmarket.zip."
Why is my battery life bad?
Your battery life is often killed when flashing ROMs in CWM. For the best battery life, you must drain your device’s battery until it turns off. Plug the device into the AC adapter and let it charge till the image says 100% charged. Then turn it on and use the volume buttons to boot into CWM. Click Wipe Battery Stats under the advanced menu. Then you should charge to 100% and install the ROM. Battery life should be comparable to (if not better than) every other ROM.
Reserved for future use!
And away we go.....
silly question but flashing method instructions...will they be included with this rom?
Yay 4 Juggs said:
silly question but flashing method instructions...will they be included with this rom?
Click to expand...
Click to collapse
Yes! Since I don't have a Photon quite yet, I won't be able to test this out. But, I posted instructions. Hopefully they work. Let me know.
p-ROM is up and ready for download. Please BETA test at your own risk! Completely untested stuff here!
very ncie work!
Anyone flash this yet?
Sent from my MoPho using XDA App
beyondinferno said:
Anyone flash this yet?
Sent from my MoPho using XDA App
Click to expand...
Click to collapse
Looking for a first victim! Worst case scenario = sbf flash.
Sent from my MB860 using XDA Premium App
Im not rooted or id be down im pretty familiar with sbf'in to save my phones life lol
kennethpenn said:
Looking for a first victim! Worst case scenario = sbf flash.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Downloading....
nunyabiziz said:
Downloading....
Click to expand...
Click to collapse
Make sure to give a nice and detailed report back. I won't have time to fix things for a while (four to five days), but I will definitely come back and mess with this p-ROM when I can.
Stuck at the boot screen for 6 minutes and counting.
nunyabiziz said:
Stuck at the boot screen for 6 minutes and counting.
Click to expand...
Click to collapse
Should be a long time, but 6 minutes sounds like a possible soft brick. Tell me if you don't get in within 4 more. Then I'll pull the download. Damn I need a test phone.
nunyabiziz said:
Stuck at the boot screen for 6 minutes and counting.
Click to expand...
Click to collapse
Did you install MR3 (flash the SBF) before installation?
Edit: If it never boots, try a battery pull and then try booting. If that doesn't work, then flash the SBF and tell me so I can pull the download.
kennethpenn said:
Did you install MR3 (flash the SBF) before installation?
Click to expand...
Click to collapse
Yes
10char
If it never boots, try a battery pull and then try booting. If that doesn't work, then flash the SBF and tell me so I can pull the download.
Flashing SBF now.
Would there be any issue if I were to use CWM recovery to restore my back up that I just made before flashing the ROM?
I havent rooted yet or Id try it. Im just sooo lost. Ive had android for a while but never Motorola. Why is Motorola so different? It just seems so different then flashing on HTC.I havent even rooted yet cuz I thought I read that that root method wouldnt let us flash Roms it was just to be able to basically run rooted apps?
nunyabiziz said:
Would there be any issue if I were to use CWM recovery to restore my back up that I just made before flashing the ROM?
Click to expand...
Click to collapse
Not sure if nandroid works on this CWM bootstrap. It wouldn't hurt to try!
aaron130 said:
I havent rooted yet or Id try it. Im just sooo lost. Ive had android for a while but never Motorola. Why is Motorola so different? It just seems so different then flashing on HTC.I havent even rooted yet cuz I thought I read that that root method wouldnt let us flash Roms it was just to be able to basically run rooted apps?
Click to expand...
Click to collapse
Your phone has a locked bootloader. Things are very similar across all Android phones, but you still need to follow the directions on the install page. SBF's are Motorola-only, that's why you've probably never heard of em.
Anybody have this problems???? I recently decided to try install the webtop hack over hdmi (by _unknown) using the cmw zip file provided by Ronaldo. after successfully hacked and used it on my TV, i now have a problem with the touchscreen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The area circled in the image, is not registering any touch. i cannot choose Motorola Widget, i cannot press the back button in Dialer, i cannot choose Sign In when you first set-up the Google Account. It seems like that line on the screen is dead or something.
i tried format data/cache/system/ in recovery mode and fastboot mode, i flashed several ROMs (Alien, Aura, piCRUST even sbf the original 4.5.91 from Motorola) to see if it's ROM-related but problem not solved. i even replaced the screen protector and its still the same.
anyone have seen this before and suggest a solution????
- Update: i also try Touchscreen Booster suggested in another thread, but still no help.
- Also, the navalynt ROM does have a new kernel, which i did flashed, but the problem is still there. i flashed back to Alien with the default kernel, the touchscreen is still messed up.
anyone suggest something???
Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.
Did you skipped the MotoBlur account setup?
If so, then try to set it up and see if that helped.
Cheers!
Rayan
Sent from my Atrix using Tapatalk
Rayan said:
Did you skipped the MotoBlur account setup?
Click to expand...
Click to collapse
i did Motoblur setup, that's why i was stuck at the Google sign-in account, had to rotate screen to select Sign In
xploited said:
Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.
Click to expand...
Click to collapse
I tried permission fix last night and the problem is still there. i also did a clean install of stock sbf 2.3.4 and fully wipe everything i can think of ( i thought it was the webtop hack that cause the problem, so i tried to delete all ) but its still there. i think this might be a hardware problem at this point. this sucks
also, my phone's root is now crazy im on Alien 4. it denied access of Quickboot but granted access to Root Explorer, which is weird.
ok, so i have tried everything i have searched on this forum: permission fix, pdsfix flash, change the value of touchpad.cfg, reflash stock sbf twice, and im still having this problem (see picture below). anyone know what is the symptoms of this ????
(i flashed ROMs occasionally, from stock to Alien, to Aura, to Homebase, i also tried webtop hack over hdmi).
anyone can help define my screen problems like in the picture???? i press one spot and the screen registers 2 touch. i now have 2 dead area on my screen.
Holy hell this is EXACTLY what my phone is doing.Except mine is randomly touching the top left corner of the screen. So when I type it enters the letter q no matter what letter I hit. Today it got so bad that everytime I hit the backspace button it would type q 5 times.
It seems asthough the multitouch hack seems to scew up the digitizer.
When I "hit" the phone (against my hand, and the phone is in a Otterbox) sometimes it would fix it. Or if a press hard on certain corners of the glass.
I reflashed the phone today to Home Base, and it hasnt done it since. I even ran Quadrant and Smart bench for a hour, while running at 1.3Ghz, and it didnt do it. So its not the phone heating up. But I am not certain its fixed. Its very random.
My only answer is the digitizer. Which is gonna suck. Not going to be as easy to fix as a iphone..
1st Post: Current status(Top), Problem (End)
2nd Post: Fix (doesn't work in the newest Build)
----------------------------------------------------------------
The Problem is back with the new 02202012 Build:
kevuin said:
kevuin said:
Oddly enough the Problem with a unresponsive area on the touchscreen is back with this new build, even when I change the Touchscreen Sensitiveness in the new Setting menu. No matter which value (yes, even 10 which had worked before), the problem was there.
Even the old way through Terminal Emulator doesn't work anymore, i guess something has been changed there.
Help !
Click to expand...
Click to collapse
codeworkx said:
are you sure it's no hardware defect? mud or water on the display?
Click to expand...
Click to collapse
That's what I had thought at the beginning too, but it went away when i flashed Stock and also when I set it the sensitivity manually with Terminal Emulator (as written here)
It's unlikely that it's just a loose contact (a.k.a. Wackelkontakt) and that it only worked when I used the Fix/stock rom..
did you change anything else in the last build that could've affected this ?
Thanks for everything BTW !
Click to expand...
Click to collapse
codeworkx said:
we just added the sgs2 settings which allows to do the same you've done via terminal emulator.
does it only happen if charger/usb cable is connected? could be a broken cable.
Click to expand...
Click to collapse
kevuin said:
That's what I thought, i just tried 'cause you never know
It's definately not because of the charger (i know the problem with some certain inofficial charger where the touchscreen stops working when plugged in. but thats not it)
It's there all the time :/ I'd guess it's because of something else you might've changed in this build then.. any other ideas ?
Click to expand...
Click to collapse
----------------------------------------------------------------
The Problem itself + everything already discussed:
After I didn't get any more help in the General Discussion Thread, I had no choice than opening another.
Here my problem and help so far:
kevuin said:
Hey Guys,
after i found some lag/problems with my touchscreen (like no response at all) sometimes, and it always helps/goes away when i turn my screen off and then back on again.
But now (idk if it's because of this build, or my hardware) i have a whole horizontal stripe not getting any information about where my fingers are at any time. That "dead" area starts after the first few pixels from the bottom (where the homebutton etc. is) and is about 1cm wide (direction top), reaching from left to right of the screen.
It's about the whole "Slide to Unlock" area on iPhones.
I thought it was a Hardware problem of mine.. so i got rid of my yellow triangle, flashed some old Stock backup i had laying around and i noticed that the problem was totally gone! next to some laggyness everywhere the area i described was acting normal !
After that i went back to CM9 and the problem is back =/
Any ideas what i can do about it or what this is caused by ?
Thanks alot !
Click to expand...
Click to collapse
mudferret said:
^ re touch screen, its because of the lpb kernel; install lp6 kernel (cm9 one, not Chainfire)
Click to expand...
Click to collapse
kevuin said:
i just flashed the kernel and oddly enough the problem is still there ! =S
now what ?
Click to expand...
Click to collapse
Additionally to all of this, I managed that my phone worked normal again (on the 02172012 Build) after I deleted the market and reinstalled from some forum because it didn't work at all.
But the touchscreen problem was back after I rebooted and wiped all caches right after.
I wasn't able to replicate this fix ever since..
so now I know it's not a hardware problem (or maybe a loose contact? ..unlikely)
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas what I can do about this ?
Any help and Ideas are welcome !
Sadly enough, this fix doesn't help anymore in the latest build
---------------------------------------------------------------------
Thanks to the fast response of XpLoDWilD everything is fixed again !
XpLoDWilD said:
Can you please run this command in Terminal Emulator (or adb shell):
Code:
echo "10" > /sys/class/sec/sec_touchscreen/tsp_threshold
and tell me if it's better ?
Click to expand...
Click to collapse
Thank you so much!!!
EDIT: For anyone who doesn't undestand
go to Terminal Emulator and type:
Code:
su
echo "10" > /sys/class/sec/sec_touchscreen/tsp_threshold
and then reboot so changes can take effect
If you have problems with touch sensivity:
XpLoDWilD said:
Just raise the "10" value. Something around 30 is nice, default is 50.
Click to expand...
Click to collapse
alsgrigorjevs also made a video about this
kevuin said:
Thanks to the fast response of XpLoDWilD everything is fixed again !
Thank you so much!!!
Click to expand...
Click to collapse
i read the thread and i will post the XploDWilD's answer, i have read that 5 min ago lol
It turned out that my phone had a Hardware defect after all, I flashed Stock and got it repaired !
Sorry if this is well known, but it took me a lot of searching to find an answer and even then it wasn't that obvious. I will explain the problem as simple as i can in case you are having it too...
At some point while running CM9/10 I started getting soft reboots everytime I plugged my phone in to transfer files. I would click the button for USB mass storage device / it would spin and then just reboot. I would see the drives on my PC but they would be light gray and not do anything when i clicked on them. This occured on a XP box a Win7 and Linux. I did the fix permissions, clear this clear that etc...
In the end it turned out that it was my Theme that was causing the issue. (Maybe someone smarter than I could chime in with why and then I can pass it on to the developer...)
I found a few posts (on and off XDA) where others were having the issue, but in one response someone with another phone/rom traced it down to their theme, removed the theme and then it worked.
In my case I can either freeze it with TB, or it seems like it's ok just switching back to system / mounting it / and then going back to the theme after.
I've seen a post for epinters CM10 build where someone referenced the problem but it cleared up on its own. I was farting around with this for about 6 hours and ready to go back to GB or ICS if needed. So hopefully if your reading this and have the same issue it will save you some frustration...
Again the Fix may be as simple as uninstalling/freezing/switching your theme to get it to work...
A huge Thanks to all the Devs that make my phone what it is... I'm an Inf/Ops guy and am always amazed how you guys can take something from concept to creation and make it work. But I could never do what you do 24/7...
Maybe a bad .9.png that is only displayed when the USB is in mass storage mode? I just went to try this for myself using epinter's 0907 build of cm10 with no extra themes installed, and it rebooted too. I could swear I just did this a few days ago with no problems. I tried again after the reboot, and it worked fine. So, I tried a third time and it rebooted again. Maybe it isn't theme related at all.
I have the same problem as you but I don't understand the solution. Can you explain it?. My rom is JellyTime R28.
Sorry for my English. Thanks
lauterm said:
Maybe a bad .9.png that is only displayed when the USB is in mass storage mode? I just went to try this for myself using epinter's 0907 build of cm10 with no extra themes installed, and it rebooted too. I could swear I just did this a few days ago with no problems. I tried again after the reboot, and it worked fine. So, I tried a third time and it rebooted again. Maybe it isn't theme related at all.
Click to expand...
Click to collapse
jsis83 said:
I have the same problem as you but I don't understand the solution. Can you explain it?. My rom is JellyTime R28.
Sorry for my English. Thanks
Click to expand...
Click to collapse
The draw9patch files that have the .9 in the end of the file name before the extension files typically wouldn't be the case. From experience, I ran into this issue multiple times when copying or editing those files manually using photoshop. If the .9 files are corrupt and do not meet the requirements set forth by the .9 specs for graphic files, the compile will fail error out and fail to complete the build instead of finishing with corrupt .9 files. It throws other weird errors when it picks up the .9 corrupt files and if you go up the terminal to see the chain of events during compiling, you'll see there was a malformed error thrown by improper alpha channels that are corrupt on the whatever file.
This USB to PC reboot error though is another annoying pain the ass error I ran into after compiling sources with changes I added to the XML code. It stems from some sort of improper code written somewhere. It's not critically an error that causes terminal errors but rather some sort of misuse of the layout coding on where things should be on the display.
I had this problem for a while when I played around with the status bar icon realigning to left or center of the screen. Although the code compiled and the build was successful and functional, this happened every single time I would connect the USB to the phone, once it reboots, I still had to disconnect and reconnect the USB cable into phone for it to properly recognize the memory card access. After taking a look at my changes to the structure of <LinearLayout children's parameters, I had some overlapping code that called for functions that weren't allowed from rules set by the parent. A little cleanup and correction, the error is completely gone and I have my end result shown in the snapshot of my status bar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cannot say 100% this is the root cause but from experience this is how I was able to create the error and then correct it to get things normally functional like they were before the error.
Out of curiosity what rom/theme are you using? Looks clean and smooth.
It's a project I've been working on daily for the last 2 months, it's a CM7 based rom I codenamed "Insight-7". Everything compiled from the CM7.2 source code and I made all tweaks, adjustments and changes to the source code directly before compiling the entire build together. I themed the entire rom with a blue\black color scheme and flashed hundreds of test builds to make sure everything works correctly in every scenario possible while maintaining a lasting battery throughout the day to be able to do anything on the phone during the day without worrying about switching batteries every few hours or looking for outlets to recharge at. I prefer to release a working & functional built rom instead of having it be alpha or beta with bugs and just provide updates to fix the bugs for months after initial release. It's reaching release to public status after I can correct a few final things so I can stress test the rom for proper functionality of each component that's worthy enough of releasing for others to use without issues.
same issue
I have a Samsung Galaxy Player 5.0 (YP-G70CWY) and used it for a few weeks until I got the itch to root and install a new rom. I successfully rooted and installed RemICS-UX Electric Catfish. I like the rom but the camera is a deal breaker given my needs unfortunately (the tablet mode was a great experience).
In my attempt to revert back to the stock rom something happened. I used Odin and successfully installed a new pit file along with the related tar. I have since done it many more times using different roms. However, with each successful Odin message the player reboots it shows the boot animation with sound and then enters into a boot loop.
I have read every post I could find on fixing boot loop for the Galaxy Player 5.0. I have carefully applied each solution without success.
Any help would be so greatly appreciated. I have rooted tablets and phones and run custom roms without problems. I am not an expert but by no means am a noob. However, I have met my match with this Player!
Thank you in advance for you time.
DankHemingway said:
I have a Samsung Galaxy Player 5.0 (YP-G70CWY) and used it for a few weeks until I got the itch to root and install a new rom. I successfully rooted and installed RemICS-UX Electric Catfish. I like the rom but the camera is a deal breaker given my needs unfortunately (the tablet mode was a great experience).
In my attempt to revert back to the stock rom something happened. I used Odin and successfully installed a new pit file along with the related tar. I have since done it many more times using different roms. However, with each successful Odin message the player reboots it shows the boot animation with sound and then enters into a boot loop.
I have read every post I could find on fixing boot loop for the Galaxy Player 5.0. I have carefully applied each solution without success.
Any help would be so greatly appreciated. I have rooted tablets and phones and run custom roms without problems. I am not an expert but by no means am a noob. However, I have met my match with this Player!
Thank you in advance for you time.
Click to expand...
Click to collapse
you need to boot into recovery (just hold power + vol up until samsung logo) and wipe data and cache. then the bootloop will (should) magically go away!
PS, have you tried cm10 or PA-JB? The camera preview is kind of messed up but it still takes pictures perfectly fine (just remember to set focus to infinity first). PA-JB has a Hybrid engine that allows you to choose not only between phone and tablet mode, but also phablet (aka nexus 7) mode!
Not trying to put down PA, but I get Gallery, PA Preferences, and random app FCs on all three times I've tried the ROM. If this is just me, I'll shut up, but that's why I stick to CM10
Sent from my YP-G70 using xda app-developers app
iurnait said:
you need to boot into recovery (just hold power + vol up until samsung logo) and wipe data and cache. then the bootloop will (should) magically go away!
PS, have you tried cm10 or PA-JB? The camera preview is kind of messed up but it still takes pictures perfectly fine (just remember to set focus to infinity first). PA-JB has a Hybrid engine that allows you to choose not only between phone and tablet mode, but also phablet (aka nexus 7) mode!
Click to expand...
Click to collapse
Thank you for the prompt reply iurnait! When I attempt to enter recovery I get this wonderful image...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
When I resolve this problem I will give both cm10 and PA-JB a chance. I just need a daily driver. Bluetooth and the camera are essential. I use Bluetooth wtih U-Connet in my car and the camera for Evernote. I can deal with a few shortcomings just not these two features.
DankHemingway said:
Thank you for the prompt reply iurnait! When I attempt to enter recovery I get this wonderful image...
.
When I resolve this problem I will give both cm10 and PA-JB a chance. I just need a daily driver. Bluetooth and the camera are essential. I use Bluetooth wtih U-Connet in my car and the camera for Evernote. I can deal with a few shortcomings just not these two features.
Click to expand...
Click to collapse
That is a picture of a forced download mode. Re-flash with Odin, and try going to recovery again. If you need both Bluetooth and camera, unfortunately you will have to stay on gingerbread for now.
That was easy. Thank you so very much. Next time I will put my pride aside a few hours earlier.
Looks like I am sticking with gb for now. Any suggestions on the best gb rom? I will probably try them all. Just hoping to avoid some unnecessary effort. I already made the mistake in upgrading without proper research and look where that got me
Thanks in advance to any suggestions!
Try chip (should be in mevordel's SIG right above your post)
Sent from my YP-G70 using xda app-developers app
iurnait said:
Try chip (should be in mevordel's SIG right above your post)
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Right on! Installing it now.
Thanks again for your help iurnait!