Hey guys.
Due to the thread closing by OP's instructions on http://forum.xda-developers.com/showthread.php?t=2422404, I've decided to continue the discussion on this thread as everyone else who was getting help on there (including myself) now can't because of that.
The idea is to help each other as the original thread's intentions were, regardless of our expertise and knowledge, because it is well-known that every small contribution can be helpful for a device or another, with enough knowledge
Just like the original thread, post your problems and solutions related to the MT6577 chipset, including porting from MT6589/MT6573/etc. devices. Politely and nicely, please.
I will start with a question I've had for a few days: Does anyone know what are the binaries and files which control the battery metering/values? In my port, I'm having a problem where a reboot takes around 20% battery, and even if the phone is with 1% remaining, it can last as much as if it has 20% remaining or something. Mine is a port of the Lenovo 4.2.2 ROM.
Any ideas?
As an note i closed it due to spamm.
(and The thread was cleaned at least 2 times)
For an base port, the info is all there.
Also The tools for port i.e.: to patch kernel ramdisk, its here on xda, an simple search will point you to that. Or you can simple use The Kitchen to extract your zlimage and replace the one in my boot.IMG as my ramdisk is already patched for 4.2.2 , and thats The one i used to patch everyones boot.img when someone requested me.
Also theres already an 2nd thread about MT6577 porting to 4.2.2
And there are fixs that are device dependent, people must understand that, and it will require work and debugging from their side!
As i said this is for advance users only, if people cant work with something simple as ADB, they shouldnt try this port.
Regarding your question, thats an known old Android bug.
The battery Stats frozing. Usually wiping cache and Dalvik fixs it for some time.
And after an ROM change you should always recalibrate your battery.
B.regards
superdragonpt said:
As an note i closed it due to spamm.
(and The thread was cleaned at least 2 times)
For an base port, the info is all there.
Also The tools for port i.e.: to patch kernel ramdisk, its here on xda, an simple search will point you to that. Or you can simple use The Kitchen to extract your zlimage and replace the one in my boot.IMG as my ramdisk is already patched for 4.2.2 , and thats The one i used to patch everyones boot.img when someone requested me.
Also theres already an 2nd thread about MT6577 porting to 4.2.2
And there are fixs that are device dependent, people must understand that, and it will require work and debugging from their side!
As i said this is for advance users only, if people cant work with something simple as ADB, they shouldnt try this port.
Regarding your question, thats an known old Android bug.
The battery Stats frozing. Usually wiping cache and Dalvik fixs it for some time.
And after an ROM change you should always recalibrate your battery.
B.regards
Click to expand...
Click to collapse
Hey man
Oh, thanks for answering on here, that was quick hehe thanks for the extra info!, I'll be sure to add it to the OP in a bit .
By the way, where is that 2nd thread? I know there is one about a tool by yuweng but it was more generic (for MT65xx and any version porting), is that the one you're refeering to?
Alright, well, I've never suffered from the battery bug until I started experimenting with this Lenovo ROM so something tells me there must be something different to it. I've used your ROMs (both 4.1 and 4.2) and never had that issue, so I'm suspecting it must be something with the ROM itself. Do you happen to know which files or binaries hold some code for the battery? I want to experiment, but with so much files around (i2c, bmt, etc) it's hard to get a starting point
About the battery stats, where are those stats located? My TWRP 2.5.0.0 doesn't have any "wipe battery stats" function and some battery stats apps I've tested can't find the stats file. Did they move it in JB 4.2 or something?
Again, thanks a lot for your advice
Thats normal, twrp and The latest CWM ( you can also try The latest up to date cwm for our ZTE, The carliv touch) that i ported, it also doesnt have that option, it was removed from The cwm source, since thats actually useless. The only thing it does is deleting one file located at /data/system/batterystats.bin this file is used ONLY for The Android battery statistics, nothing else.
If you are experience that bug more times on another ROM (port) its an indicator that some files on The ROM, are not indicated for your phone (usually its The /system/bin) files. just replaced those with your stock ones.
The thread i mention, its not that one, i will post it here later, im on The phone, so i cant use The search...
B.regards
im always stuck in bootlogo, never see the homescreen.
data connection not working
when i toggle data connection it turns on but no
icon on top
example : E , G , 3G etc
3g is not supported in my area
Related
Hi, I am a relative newbie to ROM flashing and the like. Additionally I dont have a very deep computer knowledge base. I have rooted my Samsung Captivate and have flashed a ROM (which flashed properly, but didn't quite work). I have three questions about ROM usage and such:
1. I know kernels basically add aspects to the ROM you are running, but when should you flash these? How do you flash them (same process as with ROMs? do you just do it over-top of the Rom you currently have loaded? etc...)
2. If a newer version of the ROM you have running comes out, do you have to start over and completely wipe the device over again and do the whole process from start, or can you load a newer version of your current ROM over the one you have?
3. I have been hearing/reading about some problems with the Android Market disappearing on certain ROMs when the market updates, how can i avoid this/fix this?
Thanks. Sorry the basic/stupid questions.
1. Yes
2. There are WIPE versions and NO WIPE version. Usually you can use the NO WIPE version and keep everything. But sometimes if the roms are too different you get problems and errors, then it is recommended to flash a WIPE version.
3. Hm did not experience this yet, but there are fixes somewhere .
Whats up... No question is a stupid one buddy.... (Sometimes )
To answer your first question about kernels. Flashing kernels aren't a must. You don't have to flash them really, unless there is a need. Kernels for the most part can often change the way Android handles stuff like memory management, battery resources and even multitasking. They change (tweak) the way the Android OS itself interacts with the phones hardware. That's all a kernel is really. So read up on them before flashing them because each has their advantages and disadvantages. For example, the kernel I use gives me a good RAM boost and much better battery life but it suffers on the multitasking side and I have to do other stuff to compensate for that. That's how it is. As far as flashing them is concerned. That depends. Usually, you just flash them through recovery (Like a ROM) but I would suggest you follow the instructions they give you (if it exists).
Your second question is simple. Just follow the instructions they give you for installation. Some ROMS require a full wipe and others don't. It just depends on the ROM. When in doubt, follow the instructions (again if it exists).
Your third question is a weird one, I've never heard about that really. BUT.... Some ROMS may or may not include the GAPPS applications (Google Apps).
If the ROM you flash doesn't have Google Apps built in, it would literally be missing. You would have to flash it separately. Usually in those cases though, at the download location for that ROM, they would also provide links for GAPPS zip files to flash separately so you can have the option to go with Android Market, Gmail and such OR you can use an alternative. Short of that..... never heard of that issue before..... If the issue is happening after the Market app updates, in that case it might be some type of ROM issue, you'll probably have to somehow get the updated Vending.apk (Android Market) remove/backup the original and reinstall it manually (the way you would a regular apk). I'm guessing though....
Don't you just love research........
Thanks. And now, inevitably, answers lead to more questions.
With regards to kernels, how do I know which one's do what, are compatible with which ROMs etc. I feel like its the kinda thing that needs a giant database for them, but i know there isn't.
Also, is the process for flashing other .zip files the same (though either Rom manager or a built in Recovery option). For example, a bootanimation.zip?
Ultimately I hate the idea of asking overly simply questions, but I just don't know what I dont know, nor what is supposedly implied. Thanks.
Don't sweat it...... I'm in the same boat so I have no hangups....
I think I know what you mean when it comes to kernels. Ultimately, learning about kernels requires a lot of reading in many forums (Just like this one)... Why?.... Because in many instances the persons posting the kernels might not always give you an exact breakdown on exactly what it does..... so I understand. Your best bet would be scanning XDA. I've found all sorts of really excellent kernels lying around and the devs here love documentation so there is a good chance you'll know what it does...
You could also try DroidBasement: http://droidbasement.com/db-blog/
They actually have just what you wanted, a database....kind of. They have a very large variety of kernels for different devices so its a good place to start as well.
They also tend to do a breakdown of what each kernel is capable of, the device it should be used on and so on.
About flashing zip files. Generally speaking, most zip files are flashed through recovery but its not written in stone. Following the instructions concerning said zip files are always very important. Always look for instructions before you do so at least at first. In the case of bootanimation.zip.... They are not always flashable. But if it is flashable, you can flash it through recovery which would be the best method....
If you want though, you can replace the original bootanimation.zip file with the new one manually, once you have root and some type of root explorer (for example RootExplorer for Android).
Generally, the boot animation directory is usually, /System/Media so you can check to see if its there and if it is, just backup the original and replace it with the new one.... That should work... Always nandroid before doing so though.... before doing anything really....
Thanks. I actually had a question about nandroid but forgot. Basically, what is it. I realize contextually that it's a backup program and apparently works through the recovery menus. I read a ROM flashing step-by-step that mentioned it but couldnt figure out where to get it (not in the market unlike Ti-bu which i use currently).
Nandroid is a backup program that basically creates a flash image of your phone... If you've ever heard of "Ghosting" or "Imaging" a Hard Drive, its exactly the same thing.
Its really as good as it gets as far as data backup is concerned. Its also a low level backup, so even file structures would be recorded.. In other words, you can completely screw up your phone (file partitions everything!!!!) but once you can boot to recovery, your phone can be restored. That's why its so important because its your safety net....
Its not something that you can install like an apk, so its not in the market.
You would have to flash a custom recovery. If you have one already, it should be located in one of the menus (It changes depending on the type (brand) of recovery).
If you don't see the option in your recovery then its probably not custom and you're going to have to do some digging on these forums and maybe a bit of googling for instructions on exactly how to do so. Because it could change from device to device.
Nandroid also allows you to backup your sd-ext partition as well, so if you switch cards, you can restore to another card.... Its really incredibly handy and I wouldn't suggest you do anything until you can create nandroid backups....
Now, I'm having an interesting problem I posted this same thing in general Captivate forums but maybe someone who is looking at this/answering me knows. here's what i posted there:
have a Captivate that I recently flashed Di11i's 7.1.1 to, before that I had flashed my first ROM which was Serendipity 6.2. Both times I have found that I don't get incoming calls. People calling me get 2-3 rings, and then a traditional "busy signal" sound. On my end, either the phone vibrates once but the screen doesnt change from whatever screen I'm on. Or, The screen goes black like its going to the incoming call screen, but the black screens only flashes and goes away, as does a force close message box that goes away quickly without me clicking it.
Everything else on my phone works as far as I can tell, I've been running my current ROM for about 5 days without issues other than this one. This same exact problem also happened when I flashed Serendipity 6.2 (which I only kept for like a day because of this problem)
Ok....I currently use a G1 and most of my experience has been on HTC Devices. I'm not sure of how to reply to this as I have never really modded Samsung devices before. So I'm not really familiar with software and hardware differences (Like Bootloader, Recoveries, Radios and such). But based on what you're describing.... It sounds like a ROM or maybe a radio issue. Maybe its an issue with the phone app itself. If the app is somehow buggy then thats exactly what would happen. When the phone rings the phone app would try to run but then force close....
I'm guessing here, but it could also be a radio issue because you're getting a busy tone as well which is not good. Maybe the ROM requires a specific Radio version BEFORE its flashed.... Check the source of the download and determine if it requires a specific Radio version.
In my experience though, if the correct radio version isn't used for a ROM that requires it, the phone just won't boot..... but then again, I don't know what would happen on a Samsung Captivate.... Not sure if I can help on this one because I don't have any info on that type of hardware. I don't own one you see.....
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
vlen22 said:
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
Click to expand...
Click to collapse
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Its not something that you can install like an apk, so its not in the market.
zeemar007 said:
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Click to expand...
Click to collapse
The rom kernel that I downloaded, or flashing clockwork recovery mod? Like adrenylyne's kernel for the thunderbolt.
EDIT: Never mind, I found out. I didn't mean any harm if MY POST was annoying.
If you have two kernels, in a flashable zip, you can just flash them over each other to exchange them (turn off any modification the kernel did befor though, like lagfix).
New question, I had an app (quick office) that came on my captivate. Now that I've flashed di11i's 7.1 I don't have it anymore. This is particularly peculiar because all the other native apps are still here:samsungs media player from example. How do I go about getting this missing app back on my phone. I have all the backup files on my computer so I should have the .apk (although I'm not entirely sure how to install those properly) thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.
Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)
Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html
reserved for even more future use
Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium
Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.
I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.
Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium
Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium
mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.
Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+
Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl
After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
I like Aroma, thanks for pointing that out! And yes... good idea... and a lot of work
Sorry but this is not development but merely an idea.
As soon as you have something that can be downloaded or something that shows active development (Git, sources, progress reports, individual scripts) then you can pm me to reopen the thread.
PS: You can also open such a thread in the general subforum.
Hey guys, I ported the ICS rom for P500 by arjen to my P690 using dsixda's kitchen(porting tools). As you may already know, these 2 phones have more or less EVERYTHING in same except the processor speed. The latter has 800MHz while the former has 600MHz. You can hardly find a difference even in the folders within the /system directory. Anyways, I edited the updater-script, build.prop and successfully compiled the rom. As usual I tried flashing it through CWM. The installation starts perfectly. The problem now is that it won't get past the boot animation no matter how long I wait(20-25mins to be precise!) I finally had to remove the battery, get back into CWM and restore the backup. What exactly might be the problem here?
abhishek046 said:
Hey guys, I ported the ICS rom for P500 by arjen to my P690 using dsixda's kitchen(porting tools). As you may already know, these 2 phones have more or less EVERYTHING in same except the processor speed. The latter has 800MHz while the former has 600MHz. You can hardly find a difference even in the folders within the /system directory. Anyways, I edited the updater-script, build.prop and successfully compiled the rom. As usual I tried flashing it through CWM. The installation starts perfectly. The problem now is that it won't get past the boot animation no matter how long I wait(20-25mins to be precise!) I finally had to remove the battery, get back into CWM and restore the backup. What exactly might be the problem here?
Click to expand...
Click to collapse
I'm sure you wiped everything there data/Dalvik-cache/cache
if this is not to solve the problem say this rom is in beta and you have to deeply dig into that problem :cyclops:
Of course!! I've done all tht. I even changed d cm9 bootanimation, tried the stock bootanimation and even disabled it. Got the same result in all cases, either the bootanimation does not end or there's a blank screen(when animation is turned off). This time I tried it for 45mins!! I just don't understand what to do!!
abhishek046 said:
Of course!! I've done all tht. I even changed d cm9 bootanimation, tried the stock bootanimation and even disabled it. Got the same result in all cases, either the bootanimation does not end or there's a blank screen(when animation is turned off). This time I tried it for 45mins!! I just don't understand what to do!!
Click to expand...
Click to collapse
this is enough 5-10 mins to wait for
that kitchen is good only to get root and put things together then sign zipped ROM -support for porting is somewhat "experimental":cyclops:
you should start from compiling sources replace drivers previously make dif to see how much these devices are different and of course compile kernel with debug options
also don't expect to finish this in 2-3 days.
Actually there's a cm9 rom meant for the p690 but its got many bugs like camera, bluetooth,etc. The developer who's working on it doesn't have the money to buy the phone so he's stopped developing. I'm quite new to developing, so I don't have that much of an idea on fixing it.
He says the problem in the case of the camera is with the lib and he's fixing it by replacing the lib files and editing on source. What does this actually mean? Could you explain? Also are there any guide or links where I can learn these things in depth??
abhishek046 said:
Actually there's a cm9 rom meant for the p690 but its got many bugs like camera, bluetooth,etc. The developer who's working on it doesn't have the money to buy the phone so he's stopped developing. I'm quite new to developing, so I don't have that much of an idea on fixing it.
He says the problem in the case of the camera is with the lib and he's fixing it by replacing the lib files and editing on source. What does this actually mean? Could you explain? Also are there any guide or links where I can learn these things in depth??
Click to expand...
Click to collapse
pls do not blame me for this
-you need 1-2 years of experience working in C language
-then you will just stop asking
-usually you need a team
-if devices are almost the same in hardware this is a little easyer maybe your case ?! if devices are almost the same in hardware be sure about that make diff in sources to be sure... now it's starting the hard part
-this is a "developer project" and for a long while !
-just search.. take a look here
Hello there are rom custom for my sm-g350 pls ?
Izuna30 said:
Hello there are rom custom for my sm-g350 pls ?
Click to expand...
Click to collapse
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
ngoralph said:
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
Click to expand...
Click to collapse
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
frost245 said:
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
afaik it was moved as i have reported it
Gotta get this working!
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
AlexInHell said:
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
Click to expand...
Click to collapse
As far as I know, the lock shows, that you don't have the write permission on this file
Sent from my SM-G350 using XDA-Developers mobile app