Database Users

Eb 13 /cwm3/ext4 rom install issues

Hello all.
I have tried to load two custom roms that are on eb13 with ext4. I had some small hurdles which I found answers to...but had the same net result on both.
The las5t one I tried was the frozen rom.
When it is complete all seems fine and it boots to the os. When. I hit settings or applications, it starts this strange vibration pattern and then reboots without displaying the selected menu.
If this was posted.. I did not find it. Any guidence would be appreicated and sorry for any bother. My goal is to research and go at it again next week.
I did follow the whiping instructions and in both cases I went to stock 2.1 then used odin to go to eb13. Base eb13 seems stable. In eb13 I convert to ext4 using cwm3.
From trial, I then flashed acs frozen(wipex3 and so on). On reboot the issue occurs. I did not install any apps or data which was backed up.
Sent from my SPH-D700 using XDA App

Djinn23 said:
Hello all.
I have tried to load two custom roms that are on eb13 with ext4. I had some small hurdles which I found answers to...but had the same net result on both.
The las5t one I tried was the frozen rom.
When it is complete all seems fine and it boots to the os. When. I hit settings or applications, it starts this strange vibration pattern and then reboots without displaying the selected menu.
If this was posted.. I did not find it. Any guidence would be appreicated and sorry for any bother. My goal is to research and go at it again next week.
I did follow the whiping instructions and in both cases I went to stock 2.1 then used odin to go to eb13. Base eb13 seems stable. In eb13 I convert to ext4 using cwm3.
From trial, I then flashed acs frozen(wipex3 and so on). On reboot the issue occurs. I did not install any apps or data which was backed up.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This is a know issue on both of these ROMs. You simply have to reflash the ROM when this occurs. It only seems to happen on a fresh ext4 conversion.

Thanks for the prompt reply. I may give it a try when I don't need the precious battery life.
Thanks again.
Sent from my SPH-D700 using XDA App

I had problems too from fresh eb13>cwm3>wipe 3x>flash frozenRom. At that point I was stuck in boot with bootscreens fighting eachother. So I wiped 3x again flashed frozen again now its all good.
So try wipe 3x and flash again see if that fixes you too.
Sent from my Frozen Epic using XDA App

Got it. I sacrificed 10% but it is running. Hopefully carrieriq goodness extends the heck out of this 63 %.
Thanks for the help
Sent from my SPH-D700 using XDA App

Djinn23 said:
Got it. I sacrificed 10% but it is running. Hopefully carrieriq goodness extends the heck out of this 63 %.
Thanks for the help
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sacrificed 10% for 63%? Am I the only one confused by this?
Sent from my SPH-D700 using Tapatalk

Pyperkub said:
Sacrificed 10% for 63%? Am I the only one confused by this?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
nope, count me in. new math maybe? lol

Sorry for the confusion. I chewed 10% in reapplying the rom and such of my battery....leaving me with63% bat life left.
I should also note that after applying the rom it hugh at (the equiv of) the galaxy s screen for so long. After about 5 min I force rebooted and it came back fine.

Not to cross topics.... after flashing frozen (killer rom btw) I can't find my google searchbar widget to re-enable. I didn't think this would be part of the purged bloatware.
Any ideas how this happened and how I can gvet it back? Restore of app widgets via titanium didn't do it. Tried searching but haven't mastered the art in the xda app. Results include the hone book. I am on the road....so I can't hit a puter
*** edit ****
Never mind. Appears to be a known issue related to the search buttoon not working . Thanks
Sent from my SPH-D700 using XDA App

Done with Bonsai, what ROM is considered the next best?

I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie

Syndicate is THE best imo
PS: make sure to enable journaling right after flashing it.

Best ROM
As I'm sure you've read before, every phone acts differently. Most people seem to gravitate towards ACS or Bonsai. For me, ACS was buggy and Bonsai was, while extremely fast, the worst on battery life.
I personally have had the most luck with the current MidNight ROM and more recently Simply AOSP. Even though there seem to be hundreds of threads on tweaks and hacks, most don't seem to take well to my phone. The big ones (No CIQ, for example) seem to be included in about everything now.
Give 'em a go, see what works. I can safely recommend the two above.

Yup id go with Srf 1.1.1 (1.11?) Best imo
Sent from my SPH-D700

Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Bonsai 4.1.1
SRF 1.1.1
Midnight series
Frankenstein
Urban Fury
ACE 2.0
Supernova 3
All are great ROMs
Not sure how to get the other CWM back. I like Bonsai's recovery But, if you use Quickboot and boot into recovery it takes you to CWM and not the Bonsai recovery.
Maybe you got a bad download of the Bonsai 4.1.1? Did you try to reflash it after all the FCs? Did you post in the Bonsai forum or Bonsai thread here?
You could always Odin back to stock and just start fresh that way also. Then just root with One click and get your CWM that way.
2 rules I follow about ROMs
1. No ETAs lol
2. YMMV
Everything with our phones...is phone dependent, they are completely different from the next Epic
Edit:
Sorry to the Devs that I didnt list ROMs from! These were the ones that were just on my sd card right now!

Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Use Odin Flash back to stock ECO5 rom.
You can then Flash back to clockwork using odin following the thread instructions for the specific rom you want to work with.
I like ACS Swiss Cheese it works great as long as when you are in a stock rom you get a lock for the gps before installing swiss cheese. There are several threads that explain load order for it to install correctly. I have had it running for near month now with no problems.

Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.

Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
You should use Titanium Back and backup your information using nanroid to avoid FC errors. If just remember there newest Rom is only compatible with there own kernel. If you try another Kernel with it your won't get the stellar battery life. I am using a combination of Bonsai and anonymous gingerbread and it is working out well with me. I ran Bonsai and back up all my information on Bonsai then I flashed gingerbread and recovered the Bonsai Rom on top of it.

Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
I would definitely go e it another shot. Try using the enable_journal zip in the Bonsai Downloads section first, then flash the ROM. That should help you avoid the FC issues until you get the installation errors ironed out.
Sent from my SPH-D700 using Tapatalk

I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.

lattiboy said:
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
Click to expand...
Click to collapse
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.

This. Path of least resistance for Bonsai is definitely ODIN'ing EB13. And 4.1.1 has great battery life in my experience.
Atm, the biggest deciding factor on ROM's to use has to be whether you want to stay on Froyo or do you want to be on Gingerbread.
hayzooos said:
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
Click to expand...
Click to collapse

I would also suggest using Titanium Backup and MyBackUp root sparingly. Not that they don't work but it seems many users troubles always start with restoring old data from Titanium/MBR. I have also found SMS Backup & Restore to be a good option for those wanting to save and restore your txts over using TB/MBR which seems to foul things up when restoring txts.

Don't install any data from previous roms unless it was done by Bonsai during the install. Totally avoid any system data. Old saying: garbage in garbage out...
Sent from Bonsai 7.1.1.1

Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!

digiblur said:
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
Click to expand...
Click to collapse
You didn't need to reflash to fix the mic, it's a setting in VooDoo.

try EC05 Plus out, quick stable, and good on battery life...

I use Bonsai /w journaling. It is the only ROM that has stayed stable for weeks. Others go bonkers at some point especially w/o jounaling. No offense to ACS but I have yet to have one of their ROMs start and stay stable. Baked stuff is 2nd closest.

Acs srf 1.1.1
Sent from my SPH-D700 using XDA Premium App

I have been on Urban Fury since launch day (March 29 I think) You get 1 FC on the wallpaper app on install and that's it. I have been beta testing themes and kernels and have NEVER had data corruption or force closes other than the one on boot. It comes with Genocide kernel and Wifi Tether 3 pre 14 works great. That being said, all of the ROMs are good. Its just a matter of what you and your phone like the best
Sent from my SPH-D700 using XDA Premium App

[Diagnostic Survey] Tracking the EC09 sd card bug

I know there have been multiple threads already devoted to figuring out why EC09 is borking people's sd cards, but I'm going to try a different approach. Rather than just asking for regular comments about this, I'm going to try to encourage answers to follow a set format. Hopefully the answers in this thread will lead to a diagnosis of what's causing the trouble. I'm asking you to answer the following questions to the best of your ability (there's no right or wrong answer here, since I have absolutely no clue why this is happening:
1. Did your sd card go belly up yet?
2. If your sd card did get borked, how long were you running EC09 prior to that?
3. What ROM were you on before flashing EC09?
4. Did you disable voodoo lagfix before you flashed EC09?
5. Were you running stock EC09, Nameless, or TechnoROM (if TechnoROM, did you actually flash the full stock package first)?
6. Did you Odin the recovery listed in the OPs for Nameless and TechnoROM prior to installing either of them (if you flashed one of these ROMs over stock)?
7. What apps did you have installed at the time?
8. Do you remember which apps you had actively running at the time your card borked?
9. Was your sd card almost full when you first flashed EC09?
10. Did it happen after you turned your phone off (when you were powering it back up), or while your phone was still running?
The more answers we get to these questions, the closer we come to finding the problem and possibly a solution!
More refinements to follow, including a poll.
Another Fascinating post by my XDA app...

Does this only affect people who flashed the EC09 package? I only flashed the EC09 radio and so far so good. *knocks on wood*
Sent from my SCH-I500 using XDA App

DirgeExtinction said:
Does this only affect people who flashed the EC09 package? I only flashed the EC09 radio and so far so good. *knocks on wood*
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Correct ... this only applies to those who flashed the whole ROM.
Another Fascinating post by my XDA app...

This is quite possibly way too many questions to manage.

http://twitter.com/#!/adrynalyne/status/86912115520180225

Scrappy1 said:
This is quite possibly way too many questions to manage.
Click to expand...
Click to collapse
Just answer the ones you can remember. The poll I posted may make it easier.

Victory At Last for TSM/Adrynalyne!
nunyazz said:
http://twitter.com/#!/adrynalyne/status/86912115520180225
Click to expand...
Click to collapse
Phunktastic! Can't wait to hear how he beat the bug! Guess that makes my little survey obsolete/useless (can I get ashasaur the mod to delete the thread entirely, or is closing it the best he can do?)

jmcintire said:
Phunktastic! Can't wait to hear how he beat the bug! Guess that makes my little survey obsolete/useless (can I get ashasaur the mod to delete the thread entirely, or is closing it the best he can do?)
Click to expand...
Click to collapse
he replied its not fascinate
Sent from my SCH-I500 using XDA Premium App

xHoLyx said:
he replied its not fascinate
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
false alarm!!!!

fortesquieu said:
false alarm!!!!
Click to expand...
Click to collapse
Yup, 'fraid so. Tbolt bug.
Another Fascinating post by my XDA app...

Apparently, both sbrissen and Navenedrob feel they have fixed the sd card bug in EC09 and are now testing to see if the fixes work. The upcoming Ultimate Ginger Bang ROM will include this/these fix(es) if they are found to be effective. In the meantime, your answers in the poll in the OP will still be helpful and much appreciated.
Another Fascinating post by my XDA app...

A test build for TSM's upcoming EC09 GB-based ROM is now available on irc (#teamsbrissenmod). Known issues include the following: if there is an sd card fix, it would be in the rfs kernel version of the ROM. It is unclear whether the bug has been fixed as of 7/5/11, so your help in the poll is still needed!
Another Fascinating post by my XDA app...

im on an earlier test version of Gingerbang with tsm parts and used a kerenl given to me by sbrissen and i have been on this for over a week now with no issues at all!!!
i went straight from comm rom 2.0 to the rom from sbrissen without using odin and only using heimdall do flash the modem, and kernel (kernel provided by sbrissen)
when i first went to ec09 i used the odin flash and 2 days later, dead class 2 sdcard...using a class 4 now with no issues
hope this helps in some way!

have you been able to recover the sd card or is it junk

BakedTator said:
im on an earlier test version of Gingerbang with tsm parts and used a kerenl given to me by sbrissen and i have been on this for over a week now with no issues at all!!!
i went straight from comm rom 2.0 to the rom from sbrissen without using odin and only using heimdall do flash the modem, and kernel (kernel provided by sbrissen)
when i first went to ec09 i used the odin flash and 2 days later, dead class 2 sdcard...using a class 4 now with no issues
hope this helps in some way!
Click to expand...
Click to collapse
Was sbrissen's kernel stock rfs? How fast does your phone perform?
Another Fascinating post by my XDA app...

I think my SD card just crapped out...
I had read that people that only flashed the modem weren't having issues, so that's just what i did.
Came from CommRom 2.0 straight to CM7 test build 6, had it on ED01 for a day or so and i decided to go back to Evil Fascination, and running EC01 modem for a day on that.
Then i decided to go back to CM7 test build 7, but decided to flash EC09 modem. Now it's been about 2 days, my phone was fine until about 15 mins ago when it just reboot itself and now it says damaged SD card.
Damn... i should've went back to EF last night like i wanted

I've been running the test build (rfs) for a few days now and my SD card just got wiped today. But it's weird cause it didn't wipe it entirely. The .zip files I've downloaded are still on the root of the card but it erased the download folders and such.

stereoblind said:
I've been running the test build (rfs) for a few days now and my SD card just got wiped today. But it's weird cause it didn't wipe it entirely. The .zip files I've downloaded are still on the root of the card but it erased the download folders and such.
Click to expand...
Click to collapse
Are you referring to the test build of the TSM Community EC09 build they posted on irc?
Another Fascinating post by my XDA app...

That would be the one!

Can't delete post .

Help with RandomROM Thunderhawk 3.3

Okay folks, if somebody could bring my issue to the attention of anybody who knows what to do about it I would appreciate it.
My issue is twofold:
1)I'm still getting random reboots with RandomROM Thunderhawk 3.3 despite the posting on the thread that says (NO MORE REBOOTS) Is there anything that can be done about this?
2)I checked my baseband version and the modem is still EC05, is there a way to flash or ODIN an EI22 modem for this ROM without getting a black screen when the icons should come up? Could this also be what's causing the reboots?
Thanks for anybody's help that is willing to give it.

Are you using a custom theme? And you have to flash the stickied modem delta. If you are using a theme, I would blame that.
Sent from my ICS NookColor using Tapatalk

I was using thunderhawk too and I had some reboots but onlyyyyy on the lockmod version. When I flashed the regular one I had no problems at all
And for basband I would probably try this
Nandroid backup
Flash "ec05 to ei22" its somewhere in the development section I believe
Reboot
If that doesn't work then a fresh new start is what I would Recommend
Odin back to stock
Root
Install cwm
Flash "eco5 to ei22" modem
Flash thunderhawk 3.3 (without lockmod if you could live without it)
Sent from my SPH-D700 using XDA App

I got the EI22 modem here and flashed it in CWM and it worked well. Only problem I had with thunderhawk is the lockscreen mod, and I'm having data issues on wifi after the phone's been on a while.

I was ec05 but when I flashed the Thunderhawk and it changed to ei22. never had a problem. Got a wild hair up my butt to flash the shadow kernal 1.0.6. Never been happier. no reboots, wifi works perfect, and very responsive. running a live wall paper and still get awesome battery life. give it a try

I saw several posts from folks having some wifi-4g interaction problems...switching back and forth causing one or the other to fail...is that a common problem to all 3.3 users, or are most people not seeing it? I want to give this a try, but I use 4g (at work) and wifi (home) everyday, so I'd like to see how common that issue is. I'm currently on Mostly-stock with Nubernel's latest released kernel...
Sent from my SPH-D700 using XDA App

So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App

You could always try a clean install with doing a factory data reset in CWM and wiping Dalvik, flash ROM, check to see if stuff works, then do an advanced data restore from your last nandroid. If you stll have problems then the best bet is to set everything up fresh after the clean install.

Cluefree said:
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The deal with the wifi/4g issue is that 4g will show 0.0.0.0 for ip, baseband, and dns if used after wifi in most cases. This is on official releases of 3.3 and newer. If you turn off wifi, reboot, then turn on 4g it should work. This is oviously annoying. Random provided me with alpha builds of 3.4 and 4.0, and the issue was squashed for me. However, the issue still persists in 3.4.3 official release according to some reports. I have limited access to 4g and can only test on certain days.
Thunderhawk is in a transitional period right now, and 3.4.5 should be released today. Random is hopeful this might solve some issues, including the dialer issues some are reporting with the 3.4 official builds. After that his focus will be on 4.0, which is EL30 based. Consider anything from 3.4 on a beta, and only run it if you want to help find bugs. Obviously you don't mind reporting or I wouldn't be replying lol. Just follow the threads and wait untill it looks stable enough for your usage needs.
Sent from my SPH-D700 using xda premium

Thanks! I certainly wasn't busting on Random's work...and I know he has limited access to 4g for testing, so that makes it harder for him to verify these things. So
I absolutely saw what you describe going from wifi to 4g. Going from
4g to wifi, I had wifi that wouldn't turn on at all (error when trying to enable), and, like you and others have mentioned, a reboot resolved both cases. I will hang out and see if he pushes out a fix soon, and just eagerly await 4.0. If it gets too annoying, I'll restore to my
Mostly Stock... Hmmm... Is there an issue restoring an rfs backup if I am now on ext4? Heh...
Sent from my SPH-D700 using XDA App

Just installed the latest 3.4 revision...I think...Heh. The update was so fast its hard to tell!
Sent from my SPH-D700 using XDA App

And...confirming...the wifi/4g issue persists. 4g ip address is messed up on the first connect after being on wifi...reboot resolves.
Sent from my SPH-D700 using XDA App

Random reboot

I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.

phermey said:
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
Click to expand...
Click to collapse
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes if rooted. lots of people are stock and running franco.

phermey said:
yes if rooted. lots of people are stock and running franco.
Click to expand...
Click to collapse
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.

phermey said:
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
Click to expand...
Click to collapse
wouldn't hurt to wipe anyway. ill stop wiping and see if i notice a difference though, so far i dont notice any. so id probably just skip out on wiping as it does seem useless because my phone still feels the same